CVE-2026-95107
A ThreadX module chooses `object_size` when it calls `txm_module_object_allocate`
- Risk score
- 43/100
- CVSS
- 7.0 v4.0
- Exploit chance (30 days)
- 0.2%
- Published
- 20 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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…
- Affected
- See advisory
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 7.0 high
References
Original 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.
Last activity 20 Oct 2026. Patch Forecast updates every hour.