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.
{ "versions": [ { "introduced": "0" }, { "fixed": "6.4.3" } ] }
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-55080.json"