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.
0.1%(unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-416Use After Free CWE-664Improper Control of a Resource Through its Lifetime
Show the promptExplain CVE-2026-94192 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-94192?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-94192?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-94192 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
eclipse foundation:eclipse threadx
Versions
From the CNA's record in the CVE List.
Product
Affected
Eclipse Foundation Eclipse ThreadX
from 6.0.1 through 6.5.1.202602a
Attack patterns (CAPEC)
CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
CAPEC-61 Session Fixation Likelihood: Medium · Severity: High
CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
CAPEC-196 Session Credential Falsification through Forging Likelihood: Medium · Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.