# CVE-2026-94192: Module object deallocation can free a live ThreadX kernel object


- **Severity:** High 8.5 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-57mf-w87f-rq7m

## What is CVE-2026-94192?

CVE-2026-94192 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 

### 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.

Weakness: CWE-664 (Improper Control of a Resource Through its Lifetime), CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-94192?


## How do I fix CVE-2026-94192?

No fix has been published for CVE-2026-94192 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-94192 being exploited?

There is no known exploitation of CVE-2026-94192 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94192 and fix it if it is affected.

What it is: CVE-2026-94192 is a high-severity vulnerability in Eclipse ThreadX, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-94192 in the wild and no public exploit code.

Affected product: Eclipse ThreadX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94192/ (Markdown: https://insights.sbomify.com/CVE-2026-94192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94192
- OSV: https://osv.dev/vulnerability/CVE-2026-94192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94192/
Summaries are generated and may contain mistakes; the official description above is the record.