CVE-2026-95107 Module object allocation size overflow corrupts the manager object pool
HighCVSS 7.0
EPSS 0.15%
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: partial
Description
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.
Upgrade path
1 package: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| Eclipse Foundation Eclipse ThreadX | >= 6.0.1, <= 6.5.1.202602a | after 6.5.1.202602a | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Eclipse Foundation Eclipse ThreadX | >= 6.0.1, <= 6.5.1.202602a | No fix listed |
References
- github.com
- ENISA EUVD EUVD-2026-105151 third-party-advisory