Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessExecute code in unprivileged task on MPU build
-
ExploitInvoke MPU system call with crafted buffer argument
-
ExecutionBypass region authorization check (CWE-863)
-
ImpactRead/write privileged kernel memory and escalate
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an MPU-enabled build of FreeRTOS-Kernel V11.3.0 or V11.3.1 running specifically on the Arm Cortex-R82 (Armv8-R AArch64) MPU port, and the attacker must already be able to execute an unprivileged task on the device and invoke an MPU system call with an attacker-controlled buffer argument pointing outside its assigned regions. Limiting factors: exploitation is local only (no remote/network reach), it requires pre-existing unprivileged code execution (PR:L), it does not apply to non-MPU builds or to other CPU/port targets, and it is fixed in V11.3.2 - so only the specific vulnerable port+version+MPU-mode combination is at risk. |
| Impact | All severity signals point the same direction but are tempered by exploitation prerequisites. The vendor CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:L/UI:N) scores 9.3 Critical because the vulnerable-system AND subsequent-system impacts are all High (VC/VI/VA:H, SC/SI/SA:H) - reflecting that an unprivileged task can read and write privileged kernel memory, a full confidentiality/integrity/availability compromise and a security-boundary (scope) crossing. The key limiter is that the attack is LOCAL (AV:L) and requires existing low-privilege code execution (PR:L), so this is a local privilege-escalation / memory-isolation bypass, not a remotely reachable flaw. No EPSS score, no SSVC decision data, and no POC were provided, and there is no CISA KEV listing, so there is no evidence of active or automatable exploitation - exploitation status is 'no public exploit identified at time of analysis.' Net: a genuinely high-impact issue for the specific affected configuration (Arm Cortex-R82 Armv8-R AArch64 MPU port, MPU-enabled builds) where MPU isolation is a core security guarantee, but real-world reach is constrained by the local vector, the narrow affected hardware port, and the absence of any exploitation telemetry. Treat as high priority for devices actually running the affected port; broad fleet-wide urgency is not supported by the available signals. |
| Exploit ScenarioDerived | On a device running an MPU-enabled FreeRTOS-Kernel V11.3.0/V11.3.1 build for the Arm Cortex-R82 (Armv8-R AArch64) port, an attacker who already controls an unprivileged task invokes an MPU system call and passes a crafted buffer argument that points outside the task's assigned memory regions. Because the authorization check on that buffer is incorrect (CWE-863), the kernel reads from or writes to privileged memory on the task's behalf, letting the attacker escalate to kernel privilege. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 16, 2026
FreeRTOS-Kernel V11.3.0 and V11.3.1 contain an incorrect-authorization flaw (CWE-863) in the Memory Protection Unit port for the Arm Cortex-R82 (Armv8-R AArch64), allowing 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. Exploitation is strictly local: the attacker must already be able to execute an unprivileged task on the device and invoke an MPU system call with an attacker-controlled buffer argument (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), so remote/network reach and non-MPU or non-Cortex-R82 builds are unaffected. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but the flaw is fully fixed in V11.3.2, which is the recommended upgrade target.
Earlier versions of this analysis (1)
FreeRTOS-Kernel V11.3.0 and V11.3.1 compiled as MPU-enabled builds for the Arm Cortex-R82 (Armv8-R AArch64) port fail to correctly authorize the buffer argument passed to an MPU system call, allowing a task that already runs at unprivileged level to read and write privileged kernel memory outside its assigned MPU regions - a full breach of the memory-protection isolation boundary (CVSS 3.1 8.8, AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). The attacker must already be able to execute an unprivileged task locally on the device; there is no remote or network-reachable path, and non-MPU builds and other architecture ports are not affected. No public exploit identified at time of analysis, though the prerequisite is merely low-privileged local code execution. The issue is tracked as CWE-863 (incorrect authorization) and was reported by AMZN; vendor-released patch: V11.3.2.
RemediationAI
Upgrade to FreeRTOS-Kernel V11.3.2 or later (vendor-released patch: V11.3.2, available from the vendor); the fixed source is published at https://github.com/FreeRTOS/FreeRTOS-Kernel/releases/tag/V11.3.2, with the upstream advisory at https://github.com/FreeRTOS/FreeRTOS-Kernel/security/advisories/GHSA-pv9j-rq42-3fjc and Amazon's coordinating bulletin at https://aws.amazon.com/security/security-bulletins/2026-138-aws/. If upgrading immediately is not possible, practical compensating controls are: build without MPU support or stay off the Arm Cortex-R82 MPU port for untrusted workloads, accepting that this removes the task-isolation guarantees the MPU port was adopted for; avoid creating unprivileged tasks that can call MPU system calls on affected builds, which reduces the attack surface but eliminates the intended multi-privilege task model; and wrap or interpose on MPU system calls so that application-level code bounds-checks every buffer argument against the caller's assigned region map before the kernel sees it, a mitigation that adds latency and must be audited carefully because it only protects callers that go through the wrapper. Isolation of the affected device at the hardware or hypervisor level (for example using the Cortex-R82 privilege/exception levels) limits post-exploitation reach but does not fix the in-kernel authorization defect. Note the exploit prerequisites are local only and require pre-existing unprivileged code execution, so restricting who can load or spawn tasks on the device is a meaningful interim reduction in exposure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
FreeRTOS-Kernel's MPU port implements task isolation by placing kernel data and privileged code in protected memory regions that unprivileged tasks cannot access, with MPU-related system calls acting as the controlled gateway between unprivileged tasks and privileged kernel state. On the Arm Cortex-R82 (Armv8-R AArch64) MPU port, that gateway performs insufficient validation of the buffer argument supplied by the caller: instead of verifying that the buffer lies within the calling task's assigned regions, it processes the pointer as-is. Because this is an authorization/validation failure rather than a pure memory-safety bug, it maps to CWE-863 (Incorrect Authorization), which is also why the upstream tag characterizes the issue as an authentication-bypass class problem. An unprivileged task that can reach the MPU system call can therefore construct a buffer argument that resolves into privileged kernel memory, obtaining both read and write access with a scope change (S:C) that breaks the intended MPU privilege boundary. The vulnerability is confined to MPU-enabled builds of the specific Cortex-R82/Armv8-R AArch64 port in V11.3.0 and V11.3.1; the affected component is tracked under CPE cpe:2.3:a:freertos:freertos-kernel:*:*:*:*:*:*:*:* and the EUVD record EUVD-2026-102950 lists 11.3.0 through 11.3.1 as the affected range. Because the prerequisite is local code execution as an unprivileged task (PR:L), this is a privilege-escalation and isolation-escape primitive rather than an initial-access vector.
Know when Freertos gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Requires an already-running unprivileged task so AV:L/PR:L; the unprivileged task crossing into privileged kernel memory is a scope change (S:C) with full C/I/A loss.
Primary rating from Vendor (AMZN).
CVSS VectorVendor: AMZN
Lifecycle Timeline
3DescriptionCVE.org
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.
To remediate this issue, users should upgrade to version V11.3.2 or later.
Technical POC Analysis
CWE-863 Incorrect Authorization in the Arm Cortex-R82 (Armv8-R AArch64) MPU port of FreeRTOS-Kernel.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
FreeRTOS-Kernel versions 11.3.0 and 11.3.1, used in MPU-enabled Arm Cortex-R82 embedded builds, contain a critical authorization flaw that lets a low-privileged task reach privileged kernel memory it should never access, undermining the memory isolation that safety- and security-critical device designs depend on. The exposure is constrained to devices where an attacker can already run code locally, but for organizations shipping or operating such hardware the consequence is loss of the trusted execution boundary across an entire product line. Leadership should care because remediation requires a firmware upgrade and revalidation cycle, carrying fleet-wide operational, compliance, and customer-trust implications, not just an engineering fix.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP),
Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Conne
Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Conne
Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Conne
An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP),
An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP),
An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP),
An issue was discovered in Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP),
Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Conne
Amazon Web Services (AWS) FreeRTOS through 1.3.1, FreeRTOS up to V10.0.1 (with FreeRTOS+TCP), and WITTENSTEIN WHIS Conne
The kernel in Amazon Web Services FreeRTOS before 10.4.3 has insufficient bounds checking during management of heap memo
The kernel in Amazon Web Services FreeRTOS before 10.4.3 has an integer overflow in stream_buffer.c for a stream buffer.
EUVD-2026-102950
NVD
CVE.org
GitHub
Exploit-DB