<?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>Fri, 02 Oct 2026 23:54:21 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-68296</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-68296</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-68296</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069</link>
      <description>certfr-2026-avi-1069</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1069</guid>
    </item>
    <item>
      <title>EUVD-2026-353546</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-353546</link>
      <description>EUVD-2026-353546</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-353546</guid>
    </item>
    <item>
      <title>fkie_cve-2026-68296</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-68296</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2026-68296</guid>
    </item>
    <item>
      <title>GHSA-2mgg-c98j-9pmm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2mgg-c98j-9pmm</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-2mgg-c98j-9pmm</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21910-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:21910-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23881-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:23881-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-68296</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68296</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM 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:     dev-&amp;gt;features |= GRE_FEATURES | NETIF_F_LLTX; 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.   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); 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; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM 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:     dev-&amp;gt;features |= GRE_FEATURES | NETIF_F_LLTX; 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.   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); 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://cve.radiocsirt.org/vuln/ubuntu-cve-2026-68296</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2730 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2730</guid>
    </item>
  </channel>
</rss>
