CVE-2026-53009

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-38877 (ENISA EUVD) · GHSA-67p5-53x6-9j7q (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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ice: fix double-free of tx_buf skb

If ice_tso() or ice_tx_csum() fail, the error path in ice_xmit_frame_ring() frees the skb, but the 'first' tx_buf still points to it and is marked as valid (ICE_TX_BUF_SKB). 'next_to_use' remains unchanged, so the potential problem will likely fix itself when the next packet is transmitted and the tx_buf gets overwritten. But if there is no next packet and the interface is brought down instead, ice_clean_tx_ring() -> ice_unmap_and_free_tx_buf() will find the tx_buf and free the skb for the second time.

The fix is to reset the tx_buf type to ICE_TX_BUF_EMPTY in the error path, so that ice_unmap_and_free_tx_buf(). Move the initialization of 'first' up, to ensure it's already valid in case we hit the linearization error path.

The bug was spotted by AI while I had it looking for something else. It also proposed an initial version of the patch.

I reproduced the bug and tested the fix by adding code to inject failures, on a build with KASAN.

I looked for similar bugs in related Intel drivers and did not find any.

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.2% × 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.2%
EPSS %ILE
7th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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

June 24, 2026

Last Modified

October 30, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
Patch available.
Web page

ice: fix double-free of tx_buf skb - kernel/git/stable/linux.git - Linux kernel stable tree

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

ice: fix double-free of tx_buf skb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a303baa715e6b78d6a406aaf335f87ff35acfcd

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-11-14ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-11-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-11-14ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-11-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-11-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-11-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-11-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-11-14ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-11-14ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-11-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-11-14ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-11-14ubuntu
redhatkernel-0:5.14.0-284.195.1.el9_22026-10-07redhat
redhatkernel-rt-0:5.14.0-284.195.1.rt14.480.el9_22026-10-07redhat
redhatkernel-0:6.12.0-55.105.1.el10_02026-09-21redhat
redhatkernel-0:4.18.0-372.213.1.el8_62026-09-09redhat
redhatkernel-0:5.14.0-427.149.1.el9_42026-09-09redhat
redhatkernel-0:4.18.0-553.155.1.el8_102026-08-12redhat
redhatkernel-rt-0:4.18.0-553.155.1.rt7.496.el8_102026-08-12redhat
redhatkernel-0:6.12.0-211.37.1.el10_22026-07-21redhat
linuxKernel @ 7.0.10 (fixes >=4.17.0)—osv
linuxKernel @ 6.1.191 (fixes >=4.17.0)—osv

These rows come from Ubuntu, Red Hat and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (375 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (144 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(3)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 395 rows 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. None are among the latest 100 rows. The 295 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-53009?
CVE-2026-53009 is a high-severity vulnerability; its CVE record was published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ice: fix double-free of tx_buf skb If ice_tso() or ice_tx_csum() fail, the error path in ice_xmit_frame_ring() frees the skb, but the 'first' tx_buf still points to it and is marked as valid (ICE_TX_BUF_SKB). 'next_to_use' remains…
When was the CVE record for CVE-2026-53009 published?
The CVE record for CVE-2026-53009 was published on June 24, 2026. 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-2026-53009 actively exploited?
CVE-2026-53009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53009?
CVE-2026-53009 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53009?
A fix for CVE-2026-53009 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53009 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-53009 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53009

Explore →

Is Your Infrastructure Affected by CVE-2026-53009?

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