CVE-2025-55080
HighCVSS 7.1Exploitation Probability (EPSS)
Low risk3th percentile - higher than 3% of all known CVEs
Summary
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.
Risk Assessment
An attacker could gain unauthorized memory access, potentially leading to data leakage or arbitrary code execution on the system.
Recommendation
Update Eclipse ThreadX to version 6.4.3 or later.
Other vulnerabilities in Eclipse ThreadX
See all- CVE-2025-55079Medium
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.
- CVE-2025-55078Medium
In Eclipse ThreadX before version 6.4.3, an attacker can cause a denial of service (crash) by providing a pointer to a reserved or unmapped memory region. Vulnerable system calls had a check of pointers, but that check wasn't verifying whether the pointer is outside the module memory region.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS