Memory corruption via unchecked mutex index
Published Mar 26, 2024 · Updated Feb 13, 2025
Out-of-bounds write in the Xtensa port of Eclipse ThreadX before 6.4.0 allows local users to corrupt memory during lock initialization. The _Mtxinit() function increments lcnt and passes xclib_locks[lcnt] to tx_mutex_create() even after lcnt reaches XT_NUM_CLIB_LOCKS. Exploitation requires the Xtensa XCC port with thread-safe C-library locking, user interaction, and enough lock initializations to exhaust the static array.
Summary
What happened
Out-of-bounds write in the Xtensa port of Eclipse ThreadX before 6.4.0 allows local users to corrupt memory during lock initialization. The _Mtxinit() function increments lcnt and passes xclib_locks[lcnt] to tx_mutex_create() even after lcnt reaches XT_NUM_CLIB_LOCKS. Exploitation requires the Xtensa XCC port with thread-safe C-library locking, user interaction, and enough lock initializations to exhaust the static array.
The record
- CVE
- CVE-2024-2214
- Published
- Mar 26, 2024
- Updated
- Feb 13, 2025
- Vendor
- The Eclipse Foundation
- Product
- Eclipse ThreadX
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo