CVE-2026-95108: Eclipse ThreadX Module Manager kernel stack memory leak

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

Eclipse ThreadX is an embedded real-time operating system kernel used in IoT, industrial, and automotive devices. A module manager component fails to release privileged kernel stack memory when user-mode modules delete threads, allowing a malicious or faulty module to exhaust the shared memory pool and prevent other modules from creating kernel objects or threads, causing a denial of service.

Technologies: Eclipse ThreadX. Vendors: Eclipse.

Quick answers

Is CVE-2026-95108 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-95108 being exploited in the wild.
How severe is CVE-2026-95108?
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-95108?
Yes: fixed in ThreadX 6.5.2.202603. Until then: Restrict the ability of untrusted modules to be loaded with TXM_MODULE_USER_MODE, or isolate module workloads that perform dynamic thread creation/deletion to prevent exhaustion of the shared object pool. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-95108 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-95108?
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: ThreadX 6.5.2.202603

Restrict the ability of untrusted modules to be loaded with TXM_MODULE_USER_MODE, or isolate module workloads that perform dynamic thread creation/deletion to prevent exhaustion of the shared object pool.

Technical details

When a user-mode ThreadX module creates a thread, the Module Manager allocates two objects from a shared pool: the TX_THREAD control block and a kernel stack (512–1024 bytes depending on platform). The thread-delete dispatcher only releases the control block; the kernel stack leaks and remains on the module's allocation list until the entire module stops. An attacker module can loop through thread creation and deletion to incrementally drain the pool, exhausting a finite shared resource while all operations return success.

Affected products

  • Eclipse ThreadX 6.0.1 through 6.5.1.202602a

Timeline

  • 2026-10-20: disclosed
  • 2026-10-02: advisory: GitHub Security Advisory GHSA-9hhf-6357-hpgq published

References

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