ice: fix double-free of tx_buf skb
CVE-2026-53009 · published 24 Jun 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-53009?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: d76a60ba7afb89523c88cf2ed3a044ce4180289e to < 359906450690a1d70545220bde82ba74f3fd80f8, d76a60ba7afb89523c88cf2ed3a044ce4180289e to < eb6cf492ae991e40e1e5b2d3f32ec06e9cc678db, d76a60ba7afb89523c88cf2ed3a044ce4180289e to < 910e498613d5bf4cbe5f298c2613666c38679fab, d76a60ba7afb89523c88cf2ed3a044ce4180289e to < 4c08fc2119ef0281cfa2cee007acf0a251be55f2
- Linux Linux: 4.17
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/359906450690a1d70545220bde82ba74f3fd80f8
- git.kernel.org/stable/c/eb6cf492ae991e40e1e5b2d3f32ec06e9cc678db
- git.kernel.org/stable/c/910e498613d5bf4cbe5f298c2613666c38679fab
- git.kernel.org/stable/c/4c08fc2119ef0281cfa2cee007acf0a251be55f2
- git.kernel.org/stable/c/1a303baa715e6b78d6a406aaf335f87ff35acfcd
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON