Module Manager loaders leave the manager mutex held when a module preamble's sizes overflow, blocking every later module operation
Only ThreadX 6.0.1 through 6.5.2.202603 systems that use the Module Manager and load module images through the in-place, memory, absolute or absolute extended loaders are covered. Fixed in 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 module images through the in-place, memory, absolute or absolute extended loaders Affected ThreadX 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 malformed module image with oversized data or stack size values can cause the Module Manager to stop releasing its internal lock, so every later module load, start, stop, or unload hangs until the device is reset.
Read the original description
In Eclipse ThreadX versions 6.0.1 through 6.5.2.202603, the Module Manager loaders return an overflow error without releasing the Module Manager mutex when a module preamble declares a data or stack size that overflows the allocation arithmetic. Loading such an image blocks every later module load, start, stop and unload from other threads until the system is reset.
What to do
Check whether your setup matches what the bug needs.
Systems that use the Module Manager and load module images through the in-place, memory, absolute or absolute extended loaders Affected ThreadX versions are 6.0.1 through 6.5.2.202603Upgrade 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-118052
What does this mean?
A module image with an oversized data or stack size makes the Module Manager loader leave its manager mutex held. Every other thread is then blocked from loading, starting, stopping or unloading modules until the system is reset.Source: github.com
Am I affected, and how do I check?
ThreadX versions 6.0.1 through 6.5.2.202603 are in the affected range, but only for systems that use the Module Manager and load module images through the in-place, memory, absolute or absolute extended loaders. To check, confirm the ThreadX version in use and whether the module loading path uses one of those loaders.Source: github.com
What should I do about it?
Upgrade to ThreadX 6.5.2.202603b, which contains the fix. The facts provided do not list a workaround.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