Technical impact
Eclipse ThreadX allows user‑mode, memory‑protected modules to call thread‑control functions without verifying that the target thread belongs to the calling module. Because of this missing ownership check, any loaded module can suspend, resume, terminate, reset, or re‑prioritise threads owned by other modules or the application, and it can also abort waiting operations on those threads. The result is that an attacker can deny service to legitimate threads, disrupt scheduling or cause components to behave unpredictably, all without needing elevated privileges on the host system.
Affected Systems
This flaw affects all Eclipse ThreadX releases from version 6.0.1 through 6.5.2.202603. Systems that run these editions and enable dynamic loading of third‑party modules are vulnerable.
Risk and Exploitability
The vulnerability carries a CVSS v3 score of 6.9, indicating a moderate severity. EPSS is not available and the flaw is not yet listed in the CISA KEV catalog. Because any user‑mode module can invoke the affected API, the exploitation requirement is simply the ability to load or execute a malicious module within the ThreadX environment; no additional network or privilege escalation steps are described in the advisory. The lack of an ownership check means an attacker with module load privileges can directly hijack thread behaviour, potentially leading to denial of service or unpredictable scheduling. The risk to an organization depends on how openly the system accepts third‑party modules; if the module load mechanism is tightly controlled, the threat is mitigated, but where modules can be added at run time, the flaw remains highly exploitable.