The vulnerability occurs when a ThreadX module requests deallocation of memory containing kernel object control blocks that are still in use by the operating system. The deallocation routine merely releases the memory back to the pool, leaving the object’s control block in the system’s pre‑allocated lists. If that memory is subsequently reallocated for another object before the original control block is cleared, the kernel may interpret the corrupted data, potentially leading to a crash or undefined behaviour. The flaw is a use‑after‑free condition (CWE‑416) that may also cause operating‑system state inconsistencies (CWE‑664).

This issue affects the Eclipse Foundation’s Eclipse ThreadX real‑time operating system. No explicit product or version numbers were listed in the advisory, so the flaw likely exists in all releases that employ the described module manager logic.

The flaw has a CVSS base score of 8.5, indicating high severity. EPSS information is not available and the vulnerability is not listed in the CISA KEV catalog, so no exploitation reports exist. The deallocation API is exposed only to module code that can be influenced by an attacker, which suggests the most probable attack vector is local or from malicious module code. An attacker capable of triggering a deallocation of active kernel objects could cause an immediate crash or loss of availability to the affected system.