CVE-2026-77237

In FreeRTOS-Kernel before V11.3.3, on MPU-enabled ports with queue sets enabled, missing queue-set type validation in the queue-set selection system call allows a local unprivileged task to write actor-controlled data beyond a pointer-sized object on the privileged kernel stack, affecting privileged memory across the MPU isolation boundary.

Numeric truncation of the buffer length in the MPU buffer authorization check in FreeRTOS-Kernel V11.3.0 and V11.3.1 on the Arm Cortex-R82 (Armv8-R AArch64) MPU port might allow, under certain conditions, an unprivileged task on MPU-enabled builds to read or write privileged kernel memory beyond the validated buffer window, via a stream buffer system call.

Incorrect authorization in the Arm Cortex-R82 (Armv8-R AArch64) MPU port in FreeRTOS-Kernel V11.3.0 and V11.3.1 might allow an unprivileged task on MPU-enabled builds to read and write privileged kernel memory outside the regions assigned to it, via a buffer argument passed to an MPU system call.

FreeRTOS-Kernel before version 11.3.1 lacks minimum size validation in secure context allocation, which might allow local users to corrupt secure-world heap metadata via an out-of-bounds write with an undersized stack size parameter.

FreeRTOS-Kernel before version 11.3.1 lacks privilege verification in the secure context cleanup handler, which might allow local users to cause a use-after-free condition in secure-world memory via the SVC handler for secure context deallocation.

FreeRTOS-Kernel before version 11.3.1 has improper input validation, which might allow an unprivileged task on MPU-enabled ports to execute code in privileged kernel context.