VulnerabilityPublished 24 Jun 2026Updated 6 Nov 2026

CVE-2026-53008: Linux kernel · ice: fix race condition in TX timestamp ring cleanup

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in e98cea6d5562f546482fab8ad571e95e3fff1800 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in e98cea6d5562f546482fab8ad571e95e3fff1800, 097409d20465723283632515df73038a4a853eda, 7c72ec18c2a4111204c2e915f8e4f6d849ce9398

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to e98cea6d5562f546482fab8ad571e95e3fff1800, 097409d20465723283632515df73038a4a853eda or 7c72ec18c2a4111204c2e915f8e4f6d849ce9398.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ ccde82e909467abdf098a8ee6f63e1ecf9a47ce5, < e98cea6d5562f546482fab8ad571e95e3fff1800	Fixed in e98cea6d5562f546482fab8ad571e95e3fff1800
LinuxLinux	Affected ≥ ccde82e909467abdf098a8ee6f63e1ecf9a47ce5, < 097409d20465723283632515df73038a4a853eda	Fixed in 097409d20465723283632515df73038a4a853eda
LinuxLinux	Affected ≥ ccde82e909467abdf098a8ee6f63e1ecf9a47ce5, < 7c72ec18c2a4111204c2e915f8e4f6d849ce9398	Fixed in 7c72ec18c2a4111204c2e915f8e4f6d849ce9398
LinuxLinux	Affected =6.18	Fixed in–

Description

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: 1. Reordering ice_free_tx_tstamp_ring() to clear the flag before NULLing the pointer, with smp_wmb() to ensure proper ordering. 2. 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. 3. 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

References

Community reviews

Loading reviews…