<?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>Tue, 29 Sep 2026 06:21:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43194 — net: consume xmit errors of GSO frames</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43194</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: consume xmit errors of GSO frames&lt;/p&gt;
&lt;p&gt;udpgro_frglist.sh and udpgro_bench.sh are the flakiest tests
currently in NIPA. They fail in the same exact way, TCP GRO
test stalls occasionally and the test gets killed after 10min.&lt;/p&gt;
&lt;p&gt;These tests use veth to simulate GRO. They attach a trivial
(&amp;#34;return XDP_PASS;&amp;#34;) XDP program to the veth to force TSO off
and NAPI on.&lt;/p&gt;
&lt;p&gt;Digging into the failure mode we can see that the connection
is completely stuck after a burst of drops. The sender&amp;#39;s snd_nxt
is at sequence number N [1], but the receiver claims to have
received (rcv_nxt) up to N + 3 * MSS [2]. Last piece of the puzzle
is that senders rtx queue is not empty (let&amp;#39;s say the block in
the rtx queue is at sequence number N - 4 * MSS [3]).&lt;/p&gt;
&lt;p&gt;In this state, sender sends a retransmission from the rtx queue
with a single segment, and sequence numbers N-4*MSS:N-3*MSS [3].
Receiver sees it and responds with an ACK all the way up to
N + 3 * MSS [2]. But sender will reject this ack as TCP_ACK_UNSENT_DATA
because it has no recollection of ever sending data that far out [1].
And we are stuck.&lt;/p&gt;
&lt;p&gt;The root cause is the mess of the xmit return codes. veth returns
an error when it can&amp;#39;t xmit a frame. We end up with a loss event
like this:&lt;/p&gt;
&lt;p&gt;-------------------------------------------------
  |   GSO super frame 1   |   GSO super frame 2   |
  |-----------------------------------------------|
  | seg | seg | seg | seg | seg | seg | seg | se…&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: consume xmit errors of GSO frames&lt;/p&gt;
&lt;p&gt;udpgro_frglist.sh and udpgro_bench.sh are the flakiest tests
currently in NIPA. They fail in the same exact way, TCP GRO
test stalls occasionally and the test gets killed after 10min.&lt;/p&gt;
&lt;p&gt;These tests use veth to simulate GRO. They attach a trivial
(&amp;#34;return XDP_PASS;&amp;#34;) XDP program to the veth to force TSO off
and NAPI on.&lt;/p&gt;
&lt;p&gt;Digging into the failure mode we can see that the connection
is completely stuck after a burst of drops. The sender&amp;#39;s snd_nxt
is at sequence number N [1], but the receiver claims to have
received (rcv_nxt) up to N + 3 * MSS [2]. Last piece of the puzzle
is that senders rtx queue is not empty (let&amp;#39;s say the block in
the rtx queue is at sequence number N - 4 * MSS [3]).&lt;/p&gt;
&lt;p&gt;In this state, sender sends a retransmission from the rtx queue
with a single segment, and sequence numbers N-4*MSS:N-3*MSS [3].
Receiver sees it and responds with an ACK all the way up to
N + 3 * MSS [2]. But sender will reject this ack as TCP_ACK_UNSENT_DATA
because it has no recollection of ever sending data that far out [1].
And we are stuck.&lt;/p&gt;
&lt;p&gt;The root cause is the mess of the xmit return codes. veth returns
an error when it can&amp;#39;t xmit a frame. We end up with a loss event
like this:&lt;/p&gt;
&lt;p&gt;-------------------------------------------------
  |   GSO super frame 1   |   GSO super frame 2   |
  |-----------------------------------------------|
  | seg | seg | seg | seg | seg | seg | seg | se…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43194</guid>
    </item>
  </channel>
</rss>
