dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53007

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 7.0.10 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: ice: fix potential NULL pointer deref in error path of ice_set_ringparam() ice_set_ringparam nullifies tstamp_ring of temporary tx_rings, without clearing ICE_TX_RING_FLAGS_TXTIME bit. When ICE_TX_RING_FLAGS_TXTIME is set and the subsequent ice_setup_tx_ring() call fails, a NULL pointer dereference could happen in the unwinding sequence: ice_clean_tx_ring() -> ice_is_txtime_cfg() == true (ICE_TX_RING_FLAGS_TXTIME is set) -> ice_free_tx_tstamp_ring() -> ice_free_tstamp_ring() -> tstamp_ring->desc (NULL deref) Clear ICE_TX_RING_FLAGS_TXTIME bit to avoid the potential issue. Note that this potential issue is found by manual code review. Compile test only since unfortunately I don't have E830 devices.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In the Linux kernel ice driver, ice_set_ringparam() nullifies the tstamp_ring pointer of temporary tx_rings without clearing the ICE_TX_RING_FLAGS_TXTIME flag. If ice_setup_tx_ring() subsequently fails with this flag set, the unwinding sequence in ice_clean_tx_ring() triggers ice_free_tx_tstamp_ring() which dereferences the NULL tstamp_ring pointer, causing a kernel NULL pointer dereference.

MitigationApply the upstream kernel patch to clear ICE_TX_RING_FLAGS_TXTIME when nullifying tstamp_ring in the error path of ice_set_ringparam().

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.18, < 7.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version is within affected range
    Run `uname -r` and compare to >= 6.18 and < 7.0.10
    Affected if Kernel version is 6.18.x through 7.0.9 inclusive
  2. Verify ice driver is loaded
    Run `lsmod | grep ice` or check `/sys/module/ice` exists
    Affected if The ice kernel module is loaded in memory
  3. Identify active ice network interfaces
    Run `ls /sys/class/net/` then `ethtool -i <iface>` for each to find those using the ice driver, or use `ip link show`
    Affected if Network interfaces driven by the ice driver exist and are up or configured
  4. Confirm ring parameter modification activity
    Check if `ethtool -G <ice_interface>` has been called recently, or monitor for such commands in system logs
    Affected if Ring parameters have been or are being modified on an ice-driven interface, triggering ice_set_ringparam()
  5. Verify patch status in source code
    If kernel source is available, grep for the fix in ice_set_ringparam() looking for clearing of ICE_TX_RING_FLAGS_TXTIME when tstamp_ring is nullified
    Affected if The upstream patch has not been applied and the vulnerable code path still exists

You are affected if you are running a kernel between 6.18 and 7.0.9 with the ice driver loaded and actively managing ice network interfaces, and the specific bugfix has not been applied to your kernel.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.10 or later
Fixed in 7.0.10
Interim mitigation

Apply the upstream kernel patch to clear ICE_TX_RING_FLAGS_TXTIME when nullifying tstamp_ring in the error path of ice_set_ringparam().

Recommended fix High confidence

Linux Kernel 7.0.10

  1. Upgrade the Linux kernel to version 7.0.10 or later to receive the fix for the NULL pointer dereference in ice_set_ringparam()

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53007 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53007 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data