Kernel memory corruption via signed DEVMAP indices
Published Dec 27, 2024 · Updated May 11, 2026
Out-of-bounds writes in Linux kernel BPF DEVMAP handling from 4.14 allow local users to corrupt kernel memory by deleting map elements. dev_map_delete_elem, dev_map_hash_delete_elem, and dev_map_free use signed int indices for values sourced or derived from unsigned map bounds, permitting indexing beyond the DEVMAP entry array. Reaching the flaw requires local low-privileged access capable of operating BPF DEVMAP objects; the demonstrated consequence is a kernel page fault and oops during deferred map release.
Summary
What happened
Out-of-bounds writes in Linux kernel BPF DEVMAP handling from 4.14 allow local users to corrupt kernel memory by deleting map elements. dev_map_delete_elem, dev_map_hash_delete_elem, and dev_map_free use signed int indices for values sourced or derived from unsigned map bounds, permitting indexing beyond the DEVMAP entry array. Reaching the flaw requires local low-privileged access capable of operating BPF DEVMAP objects; the demonstrated consequence is a kernel page fault and oops during deferred map release.
The record
- CVE
- CVE-2024-56615
- Published
- Dec 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 27, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.14
- Affected versionversion=546ac1ffb70d25b56c1126940e5ec639c4dd7413 <0f170e91d3063ca60baec4bd9f544faf3bfe29eb
- Affected versionversion=546ac1ffb70d25b56c1126940e5ec639c4dd7413 <178e31df1fb3d9e0890eb471da16709cbc82edee
- Affected versionversion=546ac1ffb70d25b56c1126940e5ec639c4dd7413 <70f3de869865f9c3da0508a5ea29f6f4c1889057
- Affected versionversion=546ac1ffb70d25b56c1126940e5ec639c4dd7413 <8e858930695d3ebec423e85384c95427258c294f
- Affected versionversion=546ac1ffb70d25b56c1126940e5ec639c4dd7413 <98c03d05936d846073df8f550e9e8bf0dde1d77f
- Affected versionversion=546ac1ffb70d25b56c1126940e5ec639c4dd7413 <ab244dd7cf4c291f82faacdc50b45cc0f55b674d
- Affected versionversion=546ac1ffb70d25b56c1126940e5ec639c4dd7413 <ad34306ac6836e5dd096b7d0ad4aa20cb7c8d9e5
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.
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