CVE-2024-56614: xsk: fix OOB map writes when deleting elements
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 32cd3db7de97c0c7a018756ce66244342fd583f0, 4d03f705e9d7aabebc6bfa5810f8aab6d176cbb7, d486b5741d987d3e0e6be4ac22cafdf94e6d1a47; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.
Low priority for now. Upgrade to Linux Linux 32cd3db7de97c0c7a018756ce66244342fd583f0, 4d03f705e9d7aabebc6bfa5810f8aab6d176cbb7, d486b5741d987d3e0e6be4ac22cafdf94e6d1a47; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: xsk: fix OOB map writes when deleting elements Jordy says: " In the xsk_map_delete_elem function an unsigned integer (map->max_entries) is compared with a user-controlled signed integer (k). Due to implicit type conversion, a large unsigned value for map->max_entries can bypass the intended bounds check: if (k >= map->max_entries) return -EINVAL; This allows k to hold a negative value (between -2147483648 and -2), which is then used as an array index in m->xsk_map[k], which results in an out-of-bounds access. spin_lock_bh(&m->lock); map_entry = &m->xsk_map[k]; // Out-of-bounds map_entry old_xs = unrcu_pointer(xchg(map_entry, NULL)); // Oob write if (old_xs) xsk_map_sock_delete(old_xs, map_entry); spin_unlock_bh(&m->lock); The xchg operation can then be used to cause an out-of-bounds write. Moreover, the invalid map_entry passed to xsk_map_sock_delete can lead to further memory corruption. " It indeed results in following splat: [76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108 [76612.904330] #PF: supervisor write access in kernel mode [76612.909639] #PF: error_code(0x0002) - not-present page [76612.914855] PGD 0 P4D 0 [76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP [76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470 [76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019 [76612.939781] RIP: 0010:xsk_map_delete_elem+0x2d/0x60 [76612.944738] Code: 00 00 41 54 55 53 48 63 2e 3b 6f 24 73 38 4c 8d a7 f8 00 00 00 48 89 fb 4c 89 e7 e8 2d bf 05 00 48 8d b4 eb 00 01 00 00 31 ff <48> 87 3e 48 85 ff 74 05 e8 16 ff ff ff 4c 89 e7 e8 3e bc 05 00 31 [76612.963774] RSP: 0018:ffffc9002e407df8 EFLAGS: 00010246 [76612.969079] RAX: 0000000000000000 RBX: ffffc9002e461000 RCX: 0000000000000000 [76612.976323] RDX: 0000000000000001 RSI: ffffc8fc2e461108 RDI: 0000000000000000 [76612.983569] RBP: ffffffff80000001 R08: 0000000000000000 R09: 0000000000000007 [76612.990812] R10: ffffc9002e407e18 R11: ffff888108a38858 R12: ffffc9002e4610f8 [76612.998060] R13: ffff888108a38858 R14: 00007ffd1ae0ac78 R15: ffffc9002e4610c0 [76613.005303] FS: 00007f80b6f59740(0000) GS:ffff8897e0ec0000(0000) knlGS:0000000000000000 [76613.013517] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [76613.019349] CR2: ffffc8fc2e461108 CR3: 000000011e3ef001 CR4: 00000000007726f0 [76613.026595] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [76613.033841] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [76613.041086] PKRU: 55555554 [76613.043842] Call Trace: [76613.046331] <TASK> [76613.048468] ? __die+0x20/0x60 [76613.051581] ? page_fault_oops+0x15a/0x450 [76613.055747] ? search_extable+0x22/0x30 [76613.059649] ? search_bpf_extables+0x5f/0x80 [76613.063988] ? exc_page_fault+0xa9/0x140 [76613.067975] ? asm_exc_page_fault+0x22/0x30 [76613.072229] ? xsk_map_delete_elem+0x2d/0x60 [76613.076573] ? xsk_map_delete_elem+0x23/0x60 [76613.080914] __sys_bpf+0x19b7/0x23c0 [76613.084555] __x64_sys_bpf+0x1a/0x20 [76613.088194] do_syscall_64+0x37/0xb0 [76613.091832] entry_SYSCALL_64_after_hwframe+0x4b/0x53 [76613.096962] RIP: 0033:0x7f80b6d1e88d [76613.100592] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 73 b5 0f 00 f7 d8 64 89 01 48 [76613.119631] RSP: 002b:00007ffd1ae0ac68 EFLAGS: 00000206 ORIG_RAX: 0000000000000141 [76613.131330] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f80b6d1e88d [76613.142632] RDX: 0000000000000098 RSI: 00007ffd1ae0ad20 RDI: 0000000000000003 [76613.153967] RBP: 00007ffd1ae0adc0 R08: 0000000000000000 R09: 0000000000000000 [76613.166030] R10: 00007f80b6f77040 R11: 0000000000000206 R12: 00007ffd1ae0aed8 [76613.177130] R13: 000055ddf42ce1e9 R14: 000055ddf42d0d98 R15: 00 ---truncated---
- Published
- Dec 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-787
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.18affected
- fbfc504a24f53f7ebe128ab55cb5dba634f4ece8 and later · before 4d03f705e9d7aabebc6bfa5810f8aab6d176cbb7affected · git
- fbfc504a24f53f7ebe128ab55cb5dba634f4ece8 and later · before ed08c93d5a9801cc8f224a046411fd603c538d07affected · git
- fbfc504a24f53f7ebe128ab55cb5dba634f4ece8 and later · before f8abd03f83d5fe81e76eb93e2c4373eb9f75fd8aaffected · git
- fbfc504a24f53f7ebe128ab55cb5dba634f4ece8 and later · before d486b5741d987d3e0e6be4ac22cafdf94e6d1a47affected · git
- fbfc504a24f53f7ebe128ab55cb5dba634f4ece8 and later · before 32cd3db7de97c0c7a018756ce66244342fd583f0affected · git
- before 4.18not affected · semver
- 5.15.174 and later · up to and including 5.15.*not affected · semver
- 6.1.120 and later · up to and including 6.1.*not affected · semver
- 6.6.66 and later · up to and including 6.6.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.18 and later · before 5.15.174
- linux linux kernel5.16 and later · before 6.1.120
- linux linux kernel6.2 and later · before 6.6.66
- linux linux kernel6.7 and later · before 6.12.5
- linux linux kernel6.13
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.5-1 | 6.12.5-1 |
| Red Hat:rhel_e4s:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.122.1.el9_2 | 0:7.0.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-devel | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-doc | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
| Red Hat:rhel_e4s:9.2::appstream | kernel-zfcpdump-devel-matched | before 0:5.14.0-284.122.1.el9_2 | 0:5.14.0-284.122.1.el9_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-56612Dec 27, 2024 · mm/gup: handle NULL pages in unpin_user_pages()22Monitor
- ← EarlierCVE-2024-56613Dec 27, 2024 · sched/numa: fix memory leak due to the overwritten vma->numab_state22Monitor
- Later →CVE-2024-56615Dec 27, 2024 · bpf: fix OOB devmap writes when deleting elements31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 32cd3db7de97c0c7a018756ce66244342fd583f0 | Vendor (CNA) |
| Linux Linux | 4d03f705e9d7aabebc6bfa5810f8aab6d176cbb7 | Vendor (CNA) |
| Linux Linux | d486b5741d987d3e0e6be4ac22cafdf94e6d1a47 | Vendor (CNA) |
| Linux Linux | ed08c93d5a9801cc8f224a046411fd603c538d07 | Vendor (CNA) |
| Linux Linux | f8abd03f83d5fe81e76eb93e2c4373eb9f75fd8a | Vendor (CNA) |
| azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.123-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-rt | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-core | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-extra | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo-common-x86_64 | 0:5.14.0-284.122.1.rt14.407.el9_2 · Red Hat:rhel_e4s:9.2::nfv | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4d03f705e9d7aabebc6bfa5810f8aab6d176cbb7
- git.kernel.org/stable/c/d486b5741d987d3e0e6be4ac22cafdf94e6d1a47
- git.kernel.org/stable/c/ed08c93d5a9801cc8f224a046411fd603c538d07
- git.kernel.org/stable/c/f8abd03f83d5fe81e76eb93e2c4373eb9f75fd8a
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.