CVE-2026-95107
Severity not reportedData quality: awaiting analysis.
NVD has not completed analysis, so CVSS and affected-product data may be missing or change.
A ThreadX module chooses `object_size` when it calls `txm_module_object_allocate`.
A ThreadX module chooses `object_size` when it calls `txm_module_object_allocate`. The Module Manager adds its own 16-byte private header to that size and asked the object pool for the result **without checking the addition**. A size near the top of a `ULONG` wrapped, the pool served a block far smaller than the header, and the manager then wrote the header past the end of it and into the neighbouring byte-pool block.
CVSS
—
Awaiting analysis by NVD
Timeline (UTC)
Published: 2026-10-20 16:17
Modified: 2026-10-20 19:48
NVD status: Awaiting Analysis
Last synced 1 day ago
Verified against the source API 2026-10-27 07:04 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
Data sources
NVD CVE API 2.0 — fetched 2026-10-27 07:04 UTC · record ↗