Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-53008 medium CVSS 4.7

Vulnerability in Linux kernel (CVE-2026-53008)

Summary

Vulnerability in Linux kernel (CVE-2026-53008). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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_FLAG…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-53008 has been found in Linux kernel.
Risk of unauthorized operations or information disclosure. CVSS score: 4.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2026-53008" on the vendor's site.

CVE-2026-53008 (Linux kernel) — CWE-362 / CVSS v3 4.7
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-362) exists in Linux kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel.

🔥 Severity

Severity: Medium (CVSS 4.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Linux Kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"6.18.0"},{"fixed":"6.18.57"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.0.10"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details