Kernel memory corruption via unsynchronized interconnect request list
Published May 1, 2024 · Updated Aug 5, 2026
Race condition in the Linux kernel allows local users to corrupt kernel memory through concurrent interconnect requests. The icc_set_bw() path iterates icc_node::req_list under icc_bw_lock while of_icc_get() and icc_put() can add or remove entries under only icc_lock, leaving the iterator with an invalid pointer. A low-privileged local user must repeatedly drive an interconnect-backed device path; a successful race exposes kernel memory, changes protected state, or crashes the host.
Summary
What happened
Race condition in the Linux kernel allows local users to corrupt kernel memory through concurrent interconnect requests. The icc_set_bw() path iterates icc_node::req_list under icc_bw_lock while of_icc_get() and icc_put() can add or remove entries under only icc_lock, leaving the iterator with an invalid pointer. A low-privileged local user must repeatedly drive an interconnect-backed device path; a successful race exposes kernel memory, changes protected state, or crashes the host.
The record
- CVE
- CVE-2024-27005
- Published
- May 1, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, CWE-362, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record 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=2f3a124696d43de3c837f87a9f767c56ee86cf2a
- Affected versionversion=5.15.133 <5.15.151
- Affected versionversion=6.1.55 <6.1.81
- Affected versionversion=6.5.5 <6.6
- Affected versionversion=6.6
- Affected versionversion=9be2957f014d91088db1eb5dd09d9a03d7184dce <fe549d8e976300d0dd75bd904eb216bed8b145e0
- Affected versionversion=af42269c3523492d71ebbe11fefae2653e9cdc78 <4c65507121ea8e0b47fae6d2049c8688390d46b6
- Affected versionversion=af42269c3523492d71ebbe11fefae2653e9cdc78 <d0d04efa2e367921654b5106cc5c05e3757c2b42
- Affected versionversion=af42269c3523492d71ebbe11fefae2653e9cdc78 <de1bf25b6d771abdb52d43546cf57ad775fb68a1
- Affected versionversion=ee42bfc791aa3cd78e29046f26a09d189beb3efb <19ec82b3cad1abef2a929262b8c1528f4e0c192d
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