CVE-2026-53007
Last modified
CVE-2026-53007 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.18, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53007?
How severe is CVE-2026-53007?
How do I fix CVE-2026-53007?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53001In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53002In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53003In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53004In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53005In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53006In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53008In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-53009In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5301Stored XSS in log viewer in CoolerControl/coolercontrol-ui <…6.1
- CVE-2026-53010In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53011In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53012In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53007?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
