CVE-2026-95109
8.5HighPublished 20 Oct 2026 · NVD status: Received · AI triage by gemini-3.8-flash
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-125, CWE-787
Impact
A local attacker with protected module privileges can read and write arbitrary kernel memory, gaining full control over the system. They only need the ability to execute code inside a restricted memory-protected module.
Root cause
The Cortex-A7 MMU Module validation macro checks only the first byte of a supplied buffer instead of verifying the entire length against memory boundaries.
Affected systems
Eclipse ThreadX Cortex-A7 MMU port; specific affected versions not listed — check the vendor advisory.
CVSS v4.0 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade to the patched Eclipse ThreadX release containing the fixed Cortex-A7 MMU module validation macro. If patching immediately is not possible, disable untrusted user modules or restrict module execution permissions.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
The Cortex-A7 MMU Modules port validates a caller-supplied buffer by translating **one address** — the first byte. The common Module Manager hands its range check the module instance, the start address and the complete byte size; the Cortex-A7 implementation discarded the instance and the size and asked the MMU a single question about the start. A memory-protected module therefore passed any range whose first byte was user-readable, however far the rest of it reached. Privileged dispatch code then read or wrote the whole range. Because every protected-module dispatcher that consumes a buffer or an extra-parameter array goes through this one macro, the defect is not in any individual service: it is in the primitive all of them rely on.