CVE-2026-53009
Last modified
CVE-2026-53009 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ice: fix double-free of tx_buf skb If ice_tso() or ice_tx_csum() fail, the error path in ice_xmit_frame_ring() frees the skb, but the 'first' tx_buf still points to it and is marked as valid (ICE_TX_BUF_SKB). 'next_to_use' remains unchanged, so the potential problem will likely fix itself when the next packet is transmitted and the tx_buf gets overwritten. But if there is no next packet and the interface is brought down instead, ice_clean_tx_ring() -> ice_unmap_and_free_tx_buf() will find the tx_buf and free the skb for the second time. The fix is to reset the tx_buf type to ICE_TX_BUF_EMPTY in the error path, so that ice_unmap_and_free_tx_buf(). Move the initialization of 'first' up, to ensure it's already valid in case we hit the linearization error path. The bug was spotted by AI while I had it looking for something else. It also proposed an initial version of the patch. I reproduced the bug and tested the fix by adding code to inject failures, on a build with KASAN. I looked for similar bugs in related Intel drivers and did not find any.. EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ice: fix double-free of tx_buf skb If ice_tso() or ice_tx_csum() fail, the error path in ice_xmit_frame_ring() frees the skb, but the 'first' tx_buf still points to it and is marked as valid (ICE_TX_BUF_SKB). 'next_to_use' remains unchanged, so the potential problem will likely fix itself when the next packet is transmitted and the tx_buf gets overwritten. But if there is no next packet and the interface is brought down instead, ice_clean_tx_ring() -> ice_unmap_and_free_tx_buf() will find the tx_buf and free the skb for the second time. The fix is to reset the tx_buf type to ICE_TX_BUF_EMPTY in the error path, so that ice_unmap_and_free_tx_buf(). Move the initialization of 'first' up, to ensure it's already valid in case we hit the linearization error path. The bug was spotted by AI while I had it looking for something else. It also proposed an initial version of the patch. I reproduced the bug and tested the fix by adding code to inject failures, on a build with KASAN. I looked for similar bugs in related Intel drivers and did not find any.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.17, < 7.0.10 |
| Redhat | Enterprise Linux | 7.0 |
| Redhat | Enterprise Linux | 8.0 |
| Redhat | Enterprise Linux | 9.0 |
| Redhat | Enterprise Linux | 10.0 |
References
- https://access.redhat.com/security/cve/CVE-2026-53009Third Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2492390Third Party Advisory
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53009.jsonThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-53009?
How severe is CVE-2026-53009?
How do I fix CVE-2026-53009?
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-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-53007In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53008In the Linux kernel, the following vulnerability has been re…4.7
- 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
- CVE-2026-53013In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53014In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53009?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
