Skip to main content

Linux Kernel CVE-2026-53008

| EUVDEUVD-2026-38876 MEDIUM
Race Condition (CWE-362)
2026-06-24 Linux GHSA-gqxp-fj3h-cr3v
4.7
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
4.7 MEDIUM
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

Local access only (AV:L), race condition requires precise timing (AC:H), low-privilege local user needed (PR:L), availability-only kernel crash impact (A:H), no C/I impact.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Analysis Generated
Jul 14, 2026 - 22:02 vuln.today
CVSS changed
Jul 14, 2026 - 18:52 NVD
4.7 (MEDIUM)
Patch available
Jun 24, 2026 - 18:02 EUVD
CVE Published
Jun 24, 2026 - 16:29 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

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.

  1. 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.

  1. 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

AnalysisAI

NULL pointer dereference in the Linux kernel ICE (Intel Ethernet Controller) driver allows a local low-privileged attacker to trigger a kernel panic via a race condition during TX timestamp ring teardown. The flaw exists in systems using Intel ICE-series NICs with TX timestamping configured, where concurrent execution of ice_free_tx_tstamp_ring() and ice_tx_map() across CPU cores can cause CPU B to dereference a pointer that CPU A has already set to NULL. No public exploit or active exploitation has been identified; EPSS is 0.15% (5th percentile), consistent with its local, timing-dependent nature.

Technical ContextAI

The ICE driver (drivers/net/ethernet/intel/ice/) manages TX timestamp rings for PTP hardware timestamping on Intel E810-series and related NICs. The root cause is CWE-362 (Concurrent Execution Using Shared Resource with Improper Synchronization). The teardown path (ice_free_tx_tstamp_ring()) previously nulled the tstamp_ring pointer before clearing the ICE_TX_FLAGS_TXTIME flag, lacking a store barrier. The fast path (ice_tx_map()) checked the flag via ice_is_txtime_cfg() and then read tstamp_ring without a load barrier or NULL guard, enabling a classic check-then-act TOCTOU window across cores. The fix requires: clearing the flag first with smp_wmb(), adding smp_rmb() and READ_ONCE() in the reader path, plus a NULL check as a safety net. Additionally, tx_ring->flags is converted from a plain u8 to DECLARE_BITMAP() with atomic bitops (set_bit/clear_bit/test_bit) to close any remaining non-atomic flag manipulation hazards. Affected CPE: cpe:2.3:a:linux:linux:*:*:*:*:*:*:*:*.

RemediationAI

Apply the vendor-released patch by upgrading to Linux kernel 6.18, 7.0.10, or 7.1 as appropriate to your stable branch, which include the fix commits 097409d20465723283632515df73038a4a853eda and 7c72ec18c2a4111204c2e915f8e4f6d849ce9398. Advisory and patch references: https://git.kernel.org/stable/c/097409d20465723283632515df73038a4a853eda and https://nvd.nist.gov/vuln/detail/CVE-2026-53008. If immediate patching is not feasible, a targeted workaround is to disable TX hardware timestamping on ICE interfaces using ethtool (e.g., 'ethtool -T <iface>' to confirm TXTIME support and avoid configuring SO_TXTIME sockets); this eliminates the vulnerable code path at the cost of losing PTP/hardware TX timestamp functionality. Restricting local user access to untrusted accounts on affected servers reduces the low-privilege exploitation surface. No confidentiality or integrity impact means the urgency is driven solely by kernel stability.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Performance Computing 15 SP7 Not-Affected

Share

CVE-2026-53008 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy