Quick answers
- Is CVE-2026-94192 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94192 being exploited in the wild.
- How severe is CVE-2026-94192?
- 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-94192?
- Yes: fixed in 6.5.2.202603. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94192 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-94192?
- 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
Technical details
The txm_module_object_deallocate function releases memory from the Module Manager's object pool without verifying that the kernel object is no longer in use. Deallocation does not remove the object from active kernel lists (created lists, ready lists, timer lists), so the kernel continues to dereference the freed memory. A module can then reallocate the same memory and place attacker-controlled data at the same offsets, enabling arbitrary reads and function pointer dereferences in privileged context.
Affected products
- Eclipse ThreadX 6.0.1 through 6.5.1.202602a
Timeline
- 2026-10-02: disclosed
- 2026-10-20: advisory