CVE-2025-55079Medium· 5.5▾ SunlitIn Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 30.3 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
Last analysed / modified upstream
0.2%
In Eclipse ThreadX before version 6.4.3, the thread module has a setting of maximum priority. In some cases the check of that maximum priority wasn't performed, allowing, as a result, to obtain a thread with higher priority than expected and causing a possible denial of service.
threadx < 6.4.3Upgrade past the affected range:
threadx 6.4.3Connected by shared product, vendor, weakness, or advisory.
CVE-2026-94192High· 8.5Module object deallocation can free a live ThreadX kernel object
CVE-2026-94023Medium· 6.9Module delete dispatchers do not enforce kernel-object ownership before irreversible deletion
CVE-2026-95109High· 8.5Cortex-A7 module data validation checks only the first address of a caller-supplied range
CVE-2026-94024Medium· 6.9Module Manager object lookup validates one byte of a module's search name
CVE-2026-95107High· 7.0Module object allocation size overflow corrupts the manager object pool
CVE-2026-95108Medium· 6.8Deleting a user-mode module thread leaks its privileged kernel stack