BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

CVE-2026-94192

8.5 high SSVC exploitation: none Published
NVD · CVE.org

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.

Fix

Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.

Change history 6

  1. StatusAwaiting Analysis → PublishedNVD modified 2026-10-20 17:04
  2. StatusPublished → Awaiting AnalysisNVD modified 2026-10-20 19:48
  3. StatusReceived → PublishedNVD modified 2026-10-20 17:04
  4. StatusPublished → ReceivedNVD modified 2026-10-20 18:17
  5. StatusReceived → PublishedNVD modified 2026-10-20 15:15
  6. First seenCVSS 8.5NVD modified 2026-10-20 16:17

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 1