CVE-2024-26953

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-05-01. NVD baseline CVSS 5.5; 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-24215 (ENISA EUVD) · GHSA-3rw8-47pg-9h95 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: esp: fix bad handling of pages from page_pool

When the skb is reorganized during esp_output (!esp->inline), the pages coming from the original skb fragments are supposed to be released back to the system through put_page. But if the skb fragment pages are originating from a page_pool, calling put_page on them will trigger a page_pool leak which will eventually result in a crash.

This leak can be easily observed when using CONFIG_DEBUG_VM and doing ipsec + gre (non offloaded) forwarding:

BUG: Bad page state in process ksoftirqd/16 pfn:1451b6 page:00000000de2b8d32 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1451b6000 pfn:0x1451b6 flags: 0x200000000000000(node=0|zone=2) page_type: 0xffffffff() raw: 0200000000000000 dead000000000040 ffff88810d23c000 0000000000000000 raw: 00000001451b6000 0000000000000001 00000000ffffffff 0000000000000000 page dumped because: page_pool leak Modules linked in: ip_gre gre mlx5_ib mlx5_core xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat nf_nat xt_addrtype br_netfilter rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi ib_umad rdma_cm ib_ipoib iw_cm ib_cm ib_uverbs ib_core overlay zram zsmalloc fuse [last unloaded: mlx5_core] CPU: 16 PID: 96 Comm: ksoftirqd/16 Not tainted 6.8.0-rc4+ #22 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Call Trace: dump_stack_lvl+0x36/0x50 bad_page+0x70/0xf0 free_unref_page_prepare+0x27a/0x460 free_unref_page+0x38/0x120 esp_ssg_unref.isra.0+0x15f/0x200 esp_output_tail+0x66d/0x780 esp_xmit+0x2c5/0x360 validate_xmit_xfrm+0x313/0x370 ? validate_xmit_skb+0x1d/0x330 validate_xmit_skb_list+0x4c/0x70 sch_direct_xmit+0x23e/0x350 __dev_queue_xmit+0x337/0xba0 ? nf_hook_slow+0x3f/0xd0 ip_finish_output2+0x25e/0x580 iptunnel_xmit+0x19b/0x240 ip_tunnel_xmit+0x5fb/0xb60 ipgre_xmit+0x14d/0x280 [ip_gre] dev_hard_start_xmit+0xc3/0x1c0 __dev_queue_xmit+0x208/0xba0 ? nf_hook_slow+0x3f/0xd0 ip_finish_output2+0x1ca/0x580 ip_sublist_rcv_finish+0x32/0x40 ip_sublist_rcv+0x1b2/0x1f0 ? ip_rcv_finish_core.constprop.0+0x460/0x460 ip_list_rcv+0x103/0x130 __netif_receive_skb_list_core+0x181/0x1e0 netif_receive_skb_list_internal+0x1b3/0x2c0 napi_gro_receive+0xc8/0x200 gro_cell_poll+0x52/0x90 __napi_poll+0x25/0x1a0 net_rx_action+0x28e/0x300 __do_softirq+0xc3/0x276 ? sort_range+0x20/0x20 run_ksoftirqd+0x1e/0x30 smpboot_thread_fn+0xa6/0x130 kthread+0xcd/0x100 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x31/0x50 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork_asm+0x11/0x20

The suggested fix is to introduce a new wrapper (skb_page_unref) that covers page refcounting for page_pool pages as well.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.7%
EPSS %ILE
51st
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

May 1, 2024

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated Oct 30, 2026
Patch available.
Web page

net: esp: fix bad handling of pages from page_pool - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: esp: fix bad handling of pages from page_pool - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: esp: fix bad handling of pages from page_pool - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1abb20a5f4b02fb3020f88456fc1e6069b3cdc45
Web page

net: esp: fix bad handling of pages from page_pool - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8291b4eac429c480386669444c6377573f5d8664
Web page

net: esp: fix bad handling of pages from page_pool - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21b989b62456a0e1eae9f464a5ca360a608625d1

Vendor Advisories for CVE-2024-26953(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp (6.8.0-1008.9) @ noble2026-10-30ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1006.6+1) @ noble2026-10-30ubuntu
ubuntulinux-tools-gke (6.8.0-1004.7) @ noble2026-10-30ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1006.6) @ noble2026-10-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-35.35) @ noble2026-10-30ubuntu
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.6.24 (fixes >=5.14.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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (353 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 44× 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 98 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2024-26953?
CVE-2024-26953 is a medium-severity vulnerability; its CVE record was published on May 1, 2024. In the Linux kernel, the following vulnerability has been resolved: net: esp: fix bad handling of pages from page_pool When the skb is reorganized during esp_output (!esp->inline), the pages coming from the original skb fragments are supposed to be released back to the system through put_page. But…
When was the CVE record for CVE-2024-26953 published?
The CVE record for CVE-2024-26953 was published on May 1, 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 October 30, 2026; the record at its source may have been updated since.
Is CVE-2024-26953 actively exploited?
CVE-2024-26953 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26953?
CVE-2024-26953 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26953?
A fix for CVE-2024-26953 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-26953 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-26953

Explore →

Is Your Infrastructure Affected by CVE-2024-26953?

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

Book a Demo →Browse All CVEs