CVE-2026-94023 Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion

Medium 6.9 Published Updated
Exploited in the wild
Not known
Fix
None listed

What is CVE-2026-94023?

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

Official description

A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex.

Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.

Weakness: CWE-862, CWE-125

Which versions are affected by CVE-2026-94023?

How do I fix CVE-2026-94023?

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

Is CVE-2026-94023 being exploited?

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

Sources

Also known as GHSA-36vf-7cx6-9f9j.

Is CVE-2026-94023 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free