CVE-2026-53008

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

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

ice: fix race condition in TX timestamp ring cleanup

Fix a race condition between ice_free_tx_tstamp_ring() and ice_tx_map() that can cause a NULL pointer dereference.

ice_free_tx_tstamp_ring currently clears the ICE_TX_FLAGS_TXTIME flag after NULLing the tstamp_ring. This could allow a concurrent ice_tx_map call on another CPU to dereference the tstamp_ring, which could lead to a NULL pointer dereference.

CPU A:ice_free_tx_tstamp_ring() | CPU B:ice_tx_map() --------------------------------|--------------------------------- tx_ring->tstamp_ring = NULL | | ice_is_txtime_cfg() -> true | tstamp_ring = tx_ring->tstamp_ring | tstamp_ring->count // NULL deref! flags &= ~ICE_TX_FLAGS_TXTIME |

Fix by:

  • Reordering ice_free_tx_tstamp_ring() to clear the flag before
NULLing the pointer, with smp_wmb() to ensure proper ordering.
  • Adding smp_rmb() in ice_tx_map() after the flag check to order the
flag read before the pointer read, using READ_ONCE() for the pointer, and adding a NULL check as a safety net.
  • Converting tx_ring->flags from u8 to DECLARE_BITMAP() and using
atomic bitops (set_bit(), clear_bit(), test_bit()) for all flag operations throughout the driver:
  • ICE_TX_RING_FLAGS_XDP
  • ICE_TX_RING_FLAGS_VLAN_L2TAG1
  • ICE_TX_RING_FLAGS_VLAN_L2TAG2
  • ICE_TX_RING_FLAGS_TXTIME

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

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
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 14, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
No patch confirmed yet.
generic

ice: fix race condition in TX timestamp ring cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c72ec18c2a4111204c2e915f8e4f6d849ce9398
generic

ice: fix race condition in TX timestamp ring cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/097409d20465723283632515df73038a4a853eda

Vendor Advisories for CVE-2026-53008(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 47× 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 136 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53008?
CVE-2026-53008 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ice: fix race condition in TX timestamp ring cleanup Fix a race condition between icefreetxtstampring() and icetxmap() that can cause a NULL pointer dereference. icefreetxtstampring currently clears the ICETXFLAGS_TXTIME flag after…
When was CVE-2026-53008 disclosed?
CVE-2026-53008 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53008 actively exploited?
CVE-2026-53008 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53008?
CVE-2026-53008 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-53008?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53008, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53008?

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

Start Free Scan →Browse All CVEs