GHSA-5q6x-rxf3-5q5f: User-mode module can suspend, terminate, re-prioritise and abort the waits of threads it does not own

GHSA ID

GHSA‑5q6x‑rxf3‑5q5f

CVE ID

CVE‑2026‑115654

Severity

Medium

CWE

CWE-284, CWE-862

Published

2026‑11‑01

Last updated

2026‑11‑01

Affected packages

Package Vulnerable versions Patched versions

ThreadX

>= 6.0.1, ⇐ 6.5.2.202603

6.5.2.202603b

Description

Summary

A user-mode, memory-protected module can suspend, resume, terminate, reset or re-prioritise threads it does not own, and abort their waits. The Module Manager’s thread-control dispatchers only establish that the pointer a module passes names a live thread outside the module; they do not check that the thread belongs to the calling module. Every application thread and every other module’s thread is therefore under the control of any loaded module, which can stop them permanently or change how the system schedules them.

Details

The dispatchers for tx_thread_suspend, tx_thread_resume, tx_thread_terminate, tx_thread_reset, tx_thread_priority_change, tx_thread_preemption_change, tx_thread_time_slice_change and tx_thread_wait_abort authenticate the thread pointer with _txm_module_manager_param_check_typed_object_for_use, which accepts any address that is the start of a live thread outside the calling module. Only tx_thread_delete, which requires the thread to have been allocated by the caller, and tx_thread_entry_exit_notify, which compares tx_thread_module_instance_ptr with the caller, check ownership.

A module obtains the pointers it needs through documented services: txm_module_object_pointer_get_extended finds any thread by name, and tx_thread_info_get returns the next thread on the kernel’s created list, so walking it from the module’s own thread reaches every thread in the system. _txm_module_manager_thread_reset refuses threads the application created, so reset applies only to other modules' threads.

Impact

A malicious or compromised module can deny service to the application and to other modules by suspending or terminating their threads; a terminated thread stays stopped until the application resets it. It can raise or lower other threads' priorities, preemption thresholds and time slices, resume threads their owners left suspended, and abort their waits so that blocking services return TX_WAIT_ABORTED unexpectedly. Lowering the system timer thread to the lowest priority stops every timeout and application timer from expiring while any thread of equal or higher priority stays ready. On QEMU’s MPS2 AN385 model with the Cortex-M3 module port, a user-mode module permanently stopped an application thread, changed another’s priority, aborted the module manager thread’s sleep and lowered the system timer thread’s priority. The module gains no code execution or memory access of its own through these services.

Affected configurations

Systems that use the Module Manager and load modules with memory protection, on every module port. Modules loaded without memory protection are not isolated from the kernel in any case.

Affected versions: [6.0.1, 6.5.2.202603].

Severity

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N, CVSS-B 6.9 (Medium). CWE-862: Missing Authorization; CWE-284: Improper Access Control.

VA:H because any thread can be stopped permanently; VI:L because priorities and waits can be manipulated without code execution; VC:N because only thread metadata is readable.

Patches

Fixed in ThreadX 6.5.2.202603b. For a memory-protected module, the suspend, resume, terminate, reset, priority-change, preemption-change, time-slice and wait-abort dispatchers now refuse a thread the calling module does not own with TXM_MODULE_INVALID, as tx_thread_entry_exit_notify already does. A module then controls only its own threads; an application that relies on a module suspending or resuming an application thread must use a shared synchronisation object instead. Modules without memory protection are unaffected. A new regression test fails for each dispatcher when its check is removed, and on QEMU’s mps2-an385 model every cross-owner call now returns TXM_MODULE_INVALID.

Credits

Found by Frédéric Desbiens while triaging another Module Manager report. Fixed by Frédéric Desbiens.

The analysis, fix and regression test were produced with AI assistance under human review, in accordance with the Eclipse Foundation’s Generative AI Usage Guidelines.