<?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>Thu, 01 Oct 2026 11:04:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68296 — net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68296</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: gre: fix lltx regression for GRE tunnels with SEQ/CSUM&lt;/p&gt;
&lt;p&gt;Before commit 00d066a4d4ed (&amp;#34;netdev_features: convert NETIF_F_LLTX to
dev-&amp;gt;lltx&amp;#34;), NETIF_F_LLTX was set unconditionally in both
__gre_tunnel_init() and ip6gre_tnl_init_features() alongside
GRE_FEATURES:&lt;/p&gt;
&lt;p&gt;dev-&amp;gt;features |= GRE_FEATURES | NETIF_F_LLTX;&lt;/p&gt;
&lt;p&gt;When that commit converted NETIF_F_LLTX to the dev-&amp;gt;lltx flag, it
placed &amp;#39;dev-&amp;gt;lltx = true&amp;#39; after the SEQ/CSUM early returns instead
of before them. This causes GRE/GRETAP/ip6gre tunnels with SEQ or
CSUM+encap to lose lockless TX, reintroducing _xmit_lock acquisition
around their ndo_start_xmit. Since GRE xmit re-enters the stack via
ip_tunnel_xmit(), holding _xmit_lock risks ABBA deadlock with the
underlay device.&lt;/p&gt;
&lt;p&gt;CPU0                        CPU1
  ----                        ----
  lock(&amp;amp;qdisc_xmit_lock_key#6);
                              lock(&amp;amp;qdisc_xmit_lock_key#3);
                              lock(&amp;amp;qdisc_xmit_lock_key#6);
  lock(&amp;amp;qdisc_xmit_lock_key#3);&lt;/p&gt;
&lt;p&gt;Fix by moving dev-&amp;gt;lltx = true before the early returns in both
functions, restoring the original unconditional behavior.&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: gre: fix lltx regression for GRE tunnels with SEQ/CSUM&lt;/p&gt;
&lt;p&gt;Before commit 00d066a4d4ed (&amp;#34;netdev_features: convert NETIF_F_LLTX to
dev-&amp;gt;lltx&amp;#34;), NETIF_F_LLTX was set unconditionally in both
__gre_tunnel_init() and ip6gre_tnl_init_features() alongside
GRE_FEATURES:&lt;/p&gt;
&lt;p&gt;dev-&amp;gt;features |= GRE_FEATURES | NETIF_F_LLTX;&lt;/p&gt;
&lt;p&gt;When that commit converted NETIF_F_LLTX to the dev-&amp;gt;lltx flag, it
placed &amp;#39;dev-&amp;gt;lltx = true&amp;#39; after the SEQ/CSUM early returns instead
of before them. This causes GRE/GRETAP/ip6gre tunnels with SEQ or
CSUM+encap to lose lockless TX, reintroducing _xmit_lock acquisition
around their ndo_start_xmit. Since GRE xmit re-enters the stack via
ip_tunnel_xmit(), holding _xmit_lock risks ABBA deadlock with the
underlay device.&lt;/p&gt;
&lt;p&gt;CPU0                        CPU1
  ----                        ----
  lock(&amp;amp;qdisc_xmit_lock_key#6);
                              lock(&amp;amp;qdisc_xmit_lock_key#3);
                              lock(&amp;amp;qdisc_xmit_lock_key#6);
  lock(&amp;amp;qdisc_xmit_lock_key#3);&lt;/p&gt;
&lt;p&gt;Fix by moving dev-&amp;gt;lltx = true before the early returns in both
functions, restoring the original unconditional behavior.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68296</guid>
    </item>
  </channel>
</rss>
