Kernel memory corruption via premature cpu_map write
Published Apr 2, 2024 · Updated Aug 5, 2026
Out-of-bounds write in Linux coretemp in affected kernels allows local users to corrupt kernel memory during CPU onlining. create_core_data() writes a core identifier into pdata->cpu_map[] before constraining its allocated index to the 128-entry array. The coretemp driver must process a package with more than 128 cores; module initialization or CPU onlining can then corrupt adjacent kernel memory.
Summary
What happened
Out-of-bounds write in Linux coretemp in affected kernels allows local users to corrupt kernel memory during CPU onlining. create_core_data() writes a core identifier into pdata->cpu_map[] before constraining its allocated index to the 128-entry array. The coretemp driver must process a package with more than 128 cores; module initialization or CPU onlining can then corrupt adjacent kernel memory.
The record
- CVE
- CVE-2024-26664
- Published
- Apr 2, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 2, 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=30cf0dee372baf9b515f2d9c7218f905fddf3cdb <a16afec8e83c56b14a4a73d2e3fb8eec3a8a057e
- Affected versionversion=4.19.264 <4.19.307
- Affected versionversion=4f9dcadc55c21b39b072bb0882362c7edc4340bc <93f0f4e846fcb682c3ec436e3b2e30e5a3a8ee6a
- Affected versionversion=5.10.152 <5.10.210
- Affected versionversion=5.15.76 <5.15.149
- Affected versionversion=5.4.221 <5.4.269
- Affected versionversion=6.0.6 <6.1
- Affected versionversion=6.1
- Affected versionversion=7108b80a542b9d65e44b36d64a700a83658c0b73 <3a7753bda55985dc26fae17795cb10d825453ad1
- Affected versionversion=7108b80a542b9d65e44b36d64a700a83658c0b73 <4e440abc894585a34c2904a32cd54af1742311b3
- Affected versionversion=7108b80a542b9d65e44b36d64a700a83658c0b73 <853a6503c586a71abf27e60a7f8c4fb28092976d
- Affected versionversion=7108b80a542b9d65e44b36d64a700a83658c0b73 <9bce69419271eb8b2b3ab467387cb59c99d80deb
- Affected versionversion=c00cdfc9bd767ee743ad3a4054de17aeb0afcbca <1eb74c00c9c3b13cb65e508c5d5a2f11afb96b8b
- Affected versionversion=d1de8e1ae924d9dc31548676e4a665b52ebee27e
- Affected versionversion=d9f0159da05df869071164edf0c6d7302efc5eca <f0da068c75c20ffc5ba28243ff577531dc2af1fd
What conditions does exploitation require?
What is affected?
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.
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