In Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't enough, allowing an attacker to obtain an arbitrary memory read/write.
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 1
- First seenCVSS 7.2 · eclipseNVD modified 2026-10-08 12:10
Affected (CPE criteria) 1
cpe:2.3:a:eclipse:threadx:*:*:*:*:*:*:*:*
References 1
- https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-76hh-wrj5-hr2v Third Party Advisory