High severity · published Oct 20, 2026
CVE-2026-95109
Cortex-A7 module data validation checks only the first address of a caller-supplied range
8.5
CVSS
0.1%
EPSS
No
On KEV
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.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 4% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
ET
Eclipse ThreadX · Eclipse Foundation
6.1 through 6.5.1.202602a · source: vendor
Affected product
ET
Eclipse ThreadX
Eclipse Foundation
More from Eclipse ThreadX
8.5
CVE-2026-94192
Module object deallocation can free a live ThreadX kernel object
7.0
CVE-2026-95107
Module object allocation size overflow corrupts the manager object pool
6.9
CVE-2026-94024
Module Manager object lookup validates one byte of a module's search name
6.9
CVE-2026-94023
Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion
6.8
CVE-2026-95108
Deleting a user-mode module thread leaks its privileged kernel stack