<?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>Sat, 03 Oct 2026 09:10:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-45859 — netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-45859</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;netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation&lt;/p&gt;
&lt;p&gt;Ulrich reports a regression with nfqueue:&lt;/p&gt;
&lt;p&gt;If an application did not set the &amp;#39;F_GSO&amp;#39; capability flag and a gso
packet with an unconfirmed nf_conn entry is received all packets are
now dropped instead of queued, because the check happens after
skb_gso_segment().  In that case, we did have exclusive ownership
of the skb and its associated conntrack entry.  The elevated use
count is due to skb_clone happening via skb_gso_segment().&lt;/p&gt;
&lt;p&gt;Move the check so that its peformed vs. the aggregated packet.&lt;/p&gt;
&lt;p&gt;Then, annotate the individual segments except the first one so we
can do a 2nd check at reinject time.&lt;/p&gt;
&lt;p&gt;For the normal case, where userspace does in-order reinjects, this avoids
packet drops: first reinjected segment continues traversal and confirms
entry, remaining segments observe the confirmed entry.&lt;/p&gt;
&lt;p&gt;While at it, simplify nf_ct_drop_unconfirmed(): We only care about
unconfirmed entries with a refcnt &amp;gt; 1, there is no need to special-case
dying entries.&lt;/p&gt;
&lt;p&gt;This only happens with UDP.  With TCP, the only unconfirmed packet will
be the TCP SYN, those aren&amp;#39;t aggregated by GRO.&lt;/p&gt;
&lt;p&gt;Next patch adds a udpgro test case to cover this scenario.&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;netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation&lt;/p&gt;
&lt;p&gt;Ulrich reports a regression with nfqueue:&lt;/p&gt;
&lt;p&gt;If an application did not set the &amp;#39;F_GSO&amp;#39; capability flag and a gso
packet with an unconfirmed nf_conn entry is received all packets are
now dropped instead of queued, because the check happens after
skb_gso_segment().  In that case, we did have exclusive ownership
of the skb and its associated conntrack entry.  The elevated use
count is due to skb_clone happening via skb_gso_segment().&lt;/p&gt;
&lt;p&gt;Move the check so that its peformed vs. the aggregated packet.&lt;/p&gt;
&lt;p&gt;Then, annotate the individual segments except the first one so we
can do a 2nd check at reinject time.&lt;/p&gt;
&lt;p&gt;For the normal case, where userspace does in-order reinjects, this avoids
packet drops: first reinjected segment continues traversal and confirms
entry, remaining segments observe the confirmed entry.&lt;/p&gt;
&lt;p&gt;While at it, simplify nf_ct_drop_unconfirmed(): We only care about
unconfirmed entries with a refcnt &amp;gt; 1, there is no need to special-case
dying entries.&lt;/p&gt;
&lt;p&gt;This only happens with UDP.  With TCP, the only unconfirmed packet will
be the TCP SYN, those aren&amp;#39;t aggregated by GRO.&lt;/p&gt;
&lt;p&gt;Next patch adds a udpgro test case to cover this scenario.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-45859</guid>
    </item>
  </channel>
</rss>
