{"id":"CVE-2026-95108","published":"2026-10-20T16:17:18.393","lastModified":"2026-10-20T19:48:50.250","description":"One logical thread of a user-mode ThreadX module costs the Module Manager's shared object pool two allocations, not one. The module asks for a `TX_THREAD` control block through `txm_module_object_allocate`; `_txm_module_manager_thread_create` then takes a second allocation of `TXM_MODULE_KERNEL_STACK_SIZE` bytes for the privileged kernel stack that thread's system calls run on, and records it in the control block. Both come from `_txm_module_manager_object_pool` and both are linked onto the module's allocation list.\n\n\n\nThe Module Manager's thread-delete dispatcher released only the first. The kernel stack stayed allocated until the whole module was stopped, so a module that creates, terminates and deletes threads in a loop — every state transition valid, every service returning `TX_SUCCESS` — removed a fixed block from a finite pool shared by the manager and by every other loaded module, on every cycle, for as long as it stayed loaded. Once the pool is exhausted, no memory-protected module can create any kernel object and no user-mode module thread can be created anywhere in the system.\n\n\n\nVulnerable function: `_txm_module_manager_tx_thread_delete_dispatch`, in `common_modules/module_manager/inc/txm_module_manager_dispatch.h`.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":["CWE-400","CWE-772"],"vendors":[],"products":[],"references":[{"url":"https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-9hhf-6357-hpgq","tags":[]}],"exploitRefs":[{"url":"https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-9hhf-6357-hpgq","tags":[]}],"hasPoc":true,"ai":null}