CVE-2026-53009

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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, ghsa, secondary
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • 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
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

Published

June 24, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Jun 28, 2026
Patch available.
generic

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

https://git.kernel.org/stable/c/4c08fc2119ef0281cfa2cee007acf0a251be55f2
generic

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(17)

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

(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.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 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

(11)

Data Freshness Timeline

(refreshed 7× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 297 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53009?
CVE-2026-53009 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ice: fix double-free of tx_buf skb If icetso() or icetx_csum() fail, the error path in icexmitframering() frees the skb, but the 'first' txbuf still points to it and is marked as valid (ICETXBUF_SKB). 'nexttouse' remains unchanged,…
When was CVE-2026-53009 disclosed?
CVE-2026-53009 was first published on June 24, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 Advisories panel on this page.

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.