CVE-2024-56614

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-12-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-53262 (ENISA EUVD) · GHSA-v9jf-g2rr-85c3 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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] [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---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 27, 2024

Last Modified

November 3, 2025

Advisory Details (6)

Auto-updated Oct 11, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
Web page

xsk: fix OOB map writes when deleting elements - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8abd03f83d5fe81e76eb93e2c4373eb9f75fd8a
Web page

xsk: fix OOB map writes when deleting elements - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed08c93d5a9801cc8f224a046411fd603c538d07
Web page

xsk: fix OOB map writes when deleting elements - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d486b5741d987d3e0e6be4ac22cafdf94e6d1a47
Web page

xsk: fix OOB map writes when deleting elements - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d03f705e9d7aabebc6bfa5810f8aab6d176cbb7
Web page

xsk: fix OOB map writes when deleting elements - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32cd3db7de97c0c7a018756ce66244342fd583f0

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1129.142~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-10-27ubuntu
ubuntulinux-virtual (6.8.0-56.58) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1025.30) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1077.83~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1018.19) @ noble2026-10-27ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.206) @ focal2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1090.95~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-10-27ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1024.24) @ noble2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1060 (5.4.0-1060.64) @ focal2026-10-27ubuntu
redhatkernel-0:5.14.0-427.76.1.el9_42025-07-09redhat
redhatkernel-rt-0:5.14.0-284.122.1.rt14.407.el9_22025-07-08redhat
redhatkernel-0:5.14.0-284.122.1.el9_22025-07-08redhat
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 5.15.174 (fixes >=4.18.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)
  • every version up to 6.1.123-1: fixed in 6.1.123-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.5-1: fixed in 6.12.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.5-1: fixed in 6.12.5-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(22)

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 212 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  4. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  5. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-27 19:51 UTCEG score recompute
  7. 2026-10-27 19:51 UTCVendor advisory
  8. 2026-10-27 19:51 UTCGHSA enrichmentGHSA-v9jf-g2rr-85c3 · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-25 16:55 UTCEG score recompute
  12. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  18. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  19. 2026-10-19 15:23 UTCEG score recompute
  20. 2026-10-19 15:23 UTCVendor advisory
  21. 2026-10-19 15:22 UTCGHSA enrichmentGHSA-v9jf-g2rr-85c3 · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-10-18 05:58 UTCEG score recompute
  24. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  25. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.3% · 15th percentile
Show 70 more
  1. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  2. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  3. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  4. 2026-10-12 17:37 UTCEG score recompute
  5. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  6. 2026-10-11 21:03 UTCEG score recompute
  7. 2026-10-11 15:54 UTCEG score recompute
  8. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  9. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  10. 2026-10-10 05:33 UTCOSV refresh
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  12. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  14. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  17. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  18. 2026-10-02 16:25 UTCEG score recompute
  19. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  21. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  22. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-09-20 14:44 UTCOSV refresh
  29. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  30. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  31. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  33. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  35. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  41. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  42. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  44. 2026-09-01 15:23 UTCOSV refresh
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  47. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  49. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  50. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  51. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  52. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  53. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  54. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  55. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  57. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  61. 2026-08-15 16:07 UTCOSV refresh
  62. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  64. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  65. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  66. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  67. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  68. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  69. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  70. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 16th percentile

Frequently asked(5)

What is CVE-2024-56614?
CVE-2024-56614 is a high-severity vulnerability; its CVE record was published on December 27, 2024. 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…
When was the CVE record for CVE-2024-56614 published?
The CVE record for CVE-2024-56614 was published on December 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-56614 actively exploited?
CVE-2024-56614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-56614?
CVE-2024-56614 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-56614?
A fix for CVE-2024-56614 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-56614 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-56614

Explore →

Is Your Infrastructure Affected by CVE-2024-56614?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.