<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T21:30:02.328428+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-53009</id>
    <title>CVE-2026-53009 — ice: fix double-free of tx_buf skb</title>
    <updated>2026-09-28T21:30:02.330797+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 9</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ice: fix double-free of tx_buf skb</p>
<p>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() -&gt; ice_unmap_and_free_tx_buf()
will find the tx_buf and free the skb for the second time.</p>
<p>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.</p>
<p>The bug was spotted by AI while I had it looking for something else.
It also proposed an initial version of the patch.</p>
<p>I reproduced the bug and tested the fix by adding code to inject
failures, on a build with KASAN.</p>
<p>I looked for similar bugs in related Intel drivers and did not find any.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53009"/>
  </entry>
</feed>
