Vulnerability details

CVE-2026-94192

Eclipse Foundation Eclipse ThreadX

Module object deallocation can free a live ThreadX kernel object

CVSS 4.0
8.5High

Official description

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.

CVSS scores

ScoreVersionSourceVector
8.5High 4.0 CVEProject cvelistV5 (CNA) (eclipse) CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Affected products

VendorProductVersionsSource
Eclipse Foundation Eclipse ThreadX 6.0.1 ≤ v ≤ 6.5.1.202602a CVEProject cvelistV5 (CNA)

References and advisories

1
Kolun on Telegram @kolunsec Exploited CVEs, key news and a daily digest Alerts for this product's next CVEsFollow the product to get new vulnerabilities on Telegram.

Details

Published
2026-10-20
Last updated
2026-10-20
State
Published
Assigner (CNA)
eclipse

Exploit prediction (EPSS)

0.14%
Probability of exploitation in 30 days
3.9%
Percentile (among all CVEs)

SSVC assessment (CISA)

Automatable
No
Exploitation
None
Technical impact
Total

Weaknesses (CWE)

  • CWE-416
    Use After Free
  • CWE-664
    Improper Control of a Resource Through its Lifetime