---
id: CVE-2026-94192
title: Module object deallocation can free a live ThreadX kernel object
summary: >-
  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,
  inclu…
severity: high
cvss: 8.5
cvssVector: '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'
cvssSource: cna
cwe:
  - CWE-416
  - CWE-664
vendor: Eclipse Foundation
product: ThreadX
affected:
  - ThreadX >= 6.0.1 <= 6.5.1.202602a
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-10-20T17:04:14.458746Z'
published: '2026-10-20'
updated: '2026-10-20'
sourceUpdated: '2026-10-20T17:04:24.537Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-94192'
references:
  - url: >-
      https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-57mf-w87f-rq7m
tags:
  - cve.org
ingestedAt: '2026-10-20T16:10:53.319Z'
---

## Overview

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

- `ThreadX >= 6.0.1 <= 6.5.1.202602a`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.