A ThreadX module can request the deletion of any kernel object through the Module Manager’s dispatch layer without first confirming that it owns the object. The policy used for object usage – that a module may use objects it owns or has been explicitly shared – is not applied when a module asks the dispatcher to delete an object. The module calls the function that enumerates all system objects by name, obtains pointers to objects created by any module or the system, and then instructs the dispatcher to remove the selected object. This flaw results in the removal of critical resources such as queues, semaphores, or mutexes. The loss of these objects can cause application crashes and service disruption. The description does not explicitly state that a malicious module can gain higher privileges, but if a module can delete system objects or those of privileged modules, this could undermine system stability and potentially be abused to elevate privileges. The vulnerability is a classic example of missing authorization (CWE‑862) and it involves improper ownership checks that could also lead to out‑of‑bounds reads or memory corruption (CWE‑125). If an attacker can load a malicious module or otherwise influence the Module Manager, the flaw could be used to inject a module that deletes essential kernel objects, thereby disrupting the system or compromising its reliability.

All installations of Eclipse ThreadX that use the Module Manager and dispatch services are potentially vulnerable, regardless of the specific version. The advisory does not list version numbers, so every deployment that includes the Module Manager is considered in scope. The impact applies to the Eclipse Foundation’s Eclipse ThreadX real‑time operating system.

The CVSS score of 6.9 indicates a moderate severity vulnerability. No EPSS score is available, and the vulnerability is not in the CISA KEV catalog. The likely attack vector is a module running with sufficient privileges inside the ThreadX environment that can acquire a pointer to any kernel object and request its deletion. An attacker who can deliver a malicious module could use the flaw to cause denial of service or, depending on the system’s architecture, potentially subvert system operation by removing critical objects.