CVE-2026-94024: ThreadX Module Manager object lookup boundary check bypass

CVE-2026-94024 · Severity: info · Published 2026-10-20

ThreadX is a real-time operating system kernel. A flaw in the Module Manager's object lookup function allows a memory-protected module to trigger unbounded memory reads in privileged mode. An attacker with module code can cause the kernel to read arbitrary memory and, critically, disable preemptive scheduling permanently, rendering the system unable to switch between tasks and effectively causing a denial of service.

Technologies: Eclipse ThreadX. Vendors: Eclipse.

Quick answers

Is CVE-2026-94024 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-94024 being exploited in the wild.
How severe is CVE-2026-94024?
Informational severity, published 20 October 2026.
Which products and versions are affected?
Eclipse ThreadX 6.0.1 through 6.5.1.202602a.
Is there a fix for CVE-2026-94024?
Yes: fixed in 6.5.2.202603. Until then: Disable module memory protection (set TXM_MODULE_MEMORY_PROTECTION to off), though this removes the isolation barrier. Alternatively, avoid loading untrusted modules or restrict module code execution to trusted sources only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-94024 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-94024?
Check whether you run Eclipse ThreadX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 6.5.2.202603

Disable module memory protection (set TXM_MODULE_MEMORY_PROTECTION to off), though this removes the isolation barrier. Alternatively, avoid loading untrusted modules or restrict module code execution to trusted sources only.

Technical details

The Module Manager validates only one byte of a module's search name before walking the string in privileged mode with preemption disabled. The recommended function does not use a provided length parameter to bound the buffer, while the deprecated function passes UINT_MAX, removing bounds entirely. A malicious module can register an object whose name points to its own buffer and search for it, causing the comparison to read indefinitely into adjacent memory; if a privileged read fault occurs, the preemption counter is never reset, leaving the kernel unable to preempt for the system's remaining lifetime.

Affected products

  • Eclipse ThreadX 6.0.1 through 6.5.1.202602a

Timeline

  • 2026-10-02: disclosed
  • 2026-10-20: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.