<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 21:30:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-53009 — ice: fix double-free of tx_buf skb</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-53009</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix double-free of tx_buf skb&lt;/p&gt;
&lt;p&gt;If ice_tso() or ice_tx_csum() fail, the error path in
ice_xmit_frame_ring() frees the skb, but the &amp;#39;first&amp;#39; tx_buf still points
to it and is marked as valid (ICE_TX_BUF_SKB).
&amp;#39;next_to_use&amp;#39; 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() -&amp;gt; ice_unmap_and_free_tx_buf()
will find the tx_buf and free the skb for the second time.&lt;/p&gt;
&lt;p&gt;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 &amp;#39;first&amp;#39; up, to ensure it&amp;#39;s already valid in
case we hit the linearization error path.&lt;/p&gt;
&lt;p&gt;The bug was spotted by AI while I had it looking for something else.
It also proposed an initial version of the patch.&lt;/p&gt;
&lt;p&gt;I reproduced the bug and tested the fix by adding code to inject
failures, on a build with KASAN.&lt;/p&gt;
&lt;p&gt;I looked for similar bugs in related Intel drivers and did not find any.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ice: fix double-free of tx_buf skb&lt;/p&gt;
&lt;p&gt;If ice_tso() or ice_tx_csum() fail, the error path in
ice_xmit_frame_ring() frees the skb, but the &amp;#39;first&amp;#39; tx_buf still points
to it and is marked as valid (ICE_TX_BUF_SKB).
&amp;#39;next_to_use&amp;#39; 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() -&amp;gt; ice_unmap_and_free_tx_buf()
will find the tx_buf and free the skb for the second time.&lt;/p&gt;
&lt;p&gt;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 &amp;#39;first&amp;#39; up, to ensure it&amp;#39;s already valid in
case we hit the linearization error path.&lt;/p&gt;
&lt;p&gt;The bug was spotted by AI while I had it looking for something else.
It also proposed an initial version of the patch.&lt;/p&gt;
&lt;p&gt;I reproduced the bug and tested the fix by adding code to inject
failures, on a build with KASAN.&lt;/p&gt;
&lt;p&gt;I looked for similar bugs in related Intel drivers and did not find any.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-53009</guid>
    </item>
  </channel>
</rss>
