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.
References
Link | Resource |
---|---|
https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-w8rw-fqgj-9r49 | Third Party Advisory Exploit |
Configurations
History
22 Oct 2025, 16:36
Type | Values Removed | Values Added |
---|---|---|
CPE | cpe:2.3:a:eclipse:threadx:*:*:*:*:*:*:*:* | |
References | () https://github.com/eclipse-threadx/threadx/security/advisories/GHSA-w8rw-fqgj-9r49 - Third Party Advisory, Exploit | |
First Time |
Eclipse
Eclipse threadx |
|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.5 |
15 Oct 2025, 05:16
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2025-10-15 05:16
Updated : 2025-10-22 16:36
NVD link : CVE-2025-55079
Mitre link : CVE-2025-55079
CVE.ORG link : CVE-2025-55079
JSON object : View
Products Affected
eclipse
- threadx
CWE
CWE-770
Allocation of Resources Without Limits or Throttling