<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 07:21:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80998 — net: bnxt: ring the doorbell when SW USO exits early</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-80998</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bnxt: ring the doorbell when SW USO exits early&lt;/p&gt;
&lt;p&gt;When a burst of packets is handed down to the driver, the driver defers
the doorbell to the end by setting txr-&amp;gt;kick_pending = 1. The normal TX
path handles this, but the SW USO path can miss it if it returns
early.&lt;/p&gt;
&lt;p&gt;If bnxt_sw_udp_gso_xmit runs but returns early with NETDEV_TX_BUSY and
txr-&amp;gt;kick_pending was previously set to 1, then the TX queue can
stall because the driver wrote some BDs but never wrote the doorbell.
The device won&amp;#39;t know to do the TX which would generate the completion
that would wake the queue back up.&lt;/p&gt;
&lt;p&gt;Simplify bnxt_sw_udp_gso_xmit to set txr-&amp;gt;kick_pending in its success
case and check the flag on return. The added check after
bnxt_sw_udp_gso_xmit returns ensures that any pending doorbells are
written handling both successful USO and any early returns, which
prevents the TX queue stall mentioned above.&lt;/p&gt;
&lt;p&gt;This TX queue stall was observed on a production system with a netdev TX
watchdog informing about the queue stall.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: bnxt: ring the doorbell when SW USO exits early&lt;/p&gt;
&lt;p&gt;When a burst of packets is handed down to the driver, the driver defers
the doorbell to the end by setting txr-&amp;gt;kick_pending = 1. The normal TX
path handles this, but the SW USO path can miss it if it returns
early.&lt;/p&gt;
&lt;p&gt;If bnxt_sw_udp_gso_xmit runs but returns early with NETDEV_TX_BUSY and
txr-&amp;gt;kick_pending was previously set to 1, then the TX queue can
stall because the driver wrote some BDs but never wrote the doorbell.
The device won&amp;#39;t know to do the TX which would generate the completion
that would wake the queue back up.&lt;/p&gt;
&lt;p&gt;Simplify bnxt_sw_udp_gso_xmit to set txr-&amp;gt;kick_pending in its success
case and check the flag on return. The added check after
bnxt_sw_udp_gso_xmit returns ensures that any pending doorbells are
written handling both successful USO and any early returns, which
prevents the TX queue stall mentioned above.&lt;/p&gt;
&lt;p&gt;This TX queue stall was observed on a production system with a netdev TX
watchdog informing about the queue stall.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-80998</guid>
    </item>
  </channel>
</rss>
