CVE-2026-94023
CVE-2026-94023 · Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion
Esta página presenta datos de fuentes públicas de vulnerabilidades. Consulta el aviso original antes de actualizar.
A ThreadX module reaches a kernel object's delete service through the Module Manager's dispatch layer, which asked one question about the pointer: does the object lie outside the module's own code and data. That is the policy for *using* an object, and using an object a module does not own is supported and intended — `txm_module_object_pointer_get_extended` searches the system's created objects by name and hands back objects the application created and objects other modules created, so that a module can send to a shared queue, take a shared semaphore or get a shared mutex. Destroying one of those is not sharing it. A module could name any object it had a pointer to and have the privileged dispatcher delete it.
CVSS 6.9 · Media · EPSS 0,1% · Corrección disponible
- Publicación
- Actualización
Productos y versiones afectados
eclipse threadx
- Versiones
- ≥ 6.0.1, ≤ 6.5.1.202602a: Afectada (semver)
- 6.5.2.202603: No afectada
Actualiza a 6.5.2.202603