CVE-2026-94192

published 20 Oct 2026 · updated 20 Oct 2026

Module object deallocation can free a live ThreadX kernel object

8.5HighCVSS 8.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Eclipse Foundation>=6.0.1 <=6.5.1.202602a

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-94192 severity on Zeptric[![CVE-2026-94192](https://zeptric.io/badge/cve/CVE-2026-94192.svg)](https://zeptric.io/cve/CVE-2026-94192)