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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 6
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-20 17:05
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-20 19:48
- StatusReceived → PublishedNVD modified 2026-10-20 17:05
- StatusPublished → ReceivedNVD modified 2026-10-20 18:17
- StatusReceived → PublishedNVD modified 2026-10-20 15:20
- First seenCVSS 7.0NVD modified 2026-10-20 16:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.