PoC Monitor
← All CVEs
CVE-2026-94192published 20 Oct 2026 15:15 UTCData: JSON · API

Eclipse Foundation Eclipse ThreadX

Module object deallocation can free a live ThreadX kernel object

A ThreadX module allocates the control blocks of its kernel objects from the Module Manager's object pool, and can ask for that memory back by address with `txm_module_object_deallocate`. The manager released it whatever was in it, including a control block the kernel was still using. Deallocation is not deletion: the object stays on the created list for its type, a thread stays wherever it was on the ready or suspension lists and stays schedulable, and an active timer stays on the timer list. The byte pool is meanwhile free to hand those same bytes to the next allocation.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.5high · scored by CNA · CWE-416
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Eclipse Foundation Eclipse ThreadX
  • >= 6.0.1, <= 6.5.1.202602a

Fixed in 6.5.2.202603

Mitigation

Upgrade Eclipse ThreadX to 6.5.2.202603 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published20 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.