User-mode module can suspend, terminate, re-prioritise and abort the waits of threads it does not own
Affects Eclipse ThreadX 6.0.1 through 6.5.2.202603 in systems that use the Module Manager and load modules with memory protection. Fixed in ThreadX 6.5.2.202603b.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.5.2.202603b
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Systems that use the Module Manager and load modules with memory protection, on every module port. Affected versions are 6.0.1 through 6.5.2.202603.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 12/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.5.2.202603b
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Eclipse ThreadX, a real-time operating system used in embedded devices, is affected. A user-mode module can control threads it does not own, letting it suspend, terminate, or change the priority of other threads, which can deny service or disrupt how the system schedules work.
Read the original description
In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the Module Manager's thread-control services do not check that a thread passed by a user-mode, memory-protected module belongs to that module. Any loaded module can suspend, resume, terminate, reset or re-prioritise application threads and other modules' threads and abort their waits, denying service or changing how the system schedules them.
What to do
Check whether your setup matches what the bug needs.
Systems that use the Module Manager and load modules with memory protection, on every module port. Affected versions are 6.0.1 through 6.5.2.202603.Upgrade to a fixed version: 6.5.2.202603b.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Eclipse Foundation Eclipse ThreadX
From 6.0.1 · through 6.5.2.202603
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-115654
What does this mean?
A user-mode module can suspend or terminate threads it does not own, change their priorities, preemption thresholds and time slices, or abort their thread waits. This can deny service to the application and to other modules.Source: github.com
Am I affected, and how do I check?
Eclipse ThreadX versions 6.0.1 through 6.5.2.202603 are affected, on systems that use the Module Manager and load modules with memory protection, on every module port. To check, look at the ThreadX version in use and whether the Module Manager loads modules with memory protection.Source: github.com
What should I do about it?
Upgrade to ThreadX 6.5.2.202603b, which contains the fix.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data