Cortex-A7 module data validation checks only the first address of a caller-supplied range
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.
CVE-2026-95109
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-95109
Eclipse ThreadX
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "Eclipse Foundation",
"product": "Eclipse ThreadX",
"versions": [
{
"status": "affected",
"version": "6.1",
"versionType": "custom",
"lessThanOrEqual": "6.5.1.202602a"
},
{
"status": "unaffected",
"version": "6.5.2.202603"
}
],
"packageName": "ThreadX",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-95109
Source reference:
/cveMetadata/cveId
Publisher severity
high
Source reference: /containers/cna/metrics
- Event
- #42412 · Revision 1
- Added to Heist Feed
- Publisher date