<?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 16:15:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-13689</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13689</link>
      <description>bdu:2026-13689</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13689</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-43080</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-43080</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-43080</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>EUVD-2026-323496</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-323496</link>
      <description>EUVD-2026-323496</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-323496</guid>
    </item>
    <item>
      <title>fkie_cve-2026-43080</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-43080</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;l2tp: Drop large packets with UDP encap&lt;/p&gt;
&lt;p&gt;syzbot reported a WARN on my patch series [1]. The actual issue is an
overflow of 16-bit UDP length field, and it exists in the upstream code.
My series added a debug WARN with an overflow check that exposed the
issue, that&amp;#39;s why syzbot tripped on my patches, rather than on upstream
code.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s repro:&lt;/p&gt;
&lt;p&gt;r0 = socket$pppl2tp(0x18, 0x1, 0x1)
r1 = socket$inet6_udp(0xa, 0x2, 0x0)
connect$inet6(r1, &amp;amp;(0x7f00000000c0)={0xa, 0x0, 0x0, @loopback, 0xfffffffc}, 0x1c)
connect$pppl2tp(r0, &amp;amp;(0x7f0000000240)=@pppol2tpin6={0x18, 0x1, {0x0, r1, 0x4, 0x0, 0x0, 0x0, {0xa, 0x4e22, 0xffff, @ipv4={&amp;#39;\x00&amp;#39;, &amp;#39;\xff\xff&amp;#39;, @empty}}}}, 0x32)
writev(r0, &amp;amp;(0x7f0000000080)=[{&amp;amp;(0x7f0000000000)=&amp;#34;ee&amp;#34;, 0x34000}], 0x1)&lt;/p&gt;
&lt;p&gt;It basically sends an oversized (0x34000 bytes) PPPoL2TP packet with UDP
encapsulation, and l2tp_xmit_core doesn&amp;#39;t check for overflows when it
assigns the UDP length field. The value gets trimmed to 16 bites.&lt;/p&gt;
&lt;p&gt;Add an overflow check that drops oversized packets and avoids sending
packets with trimmed UDP length to the wire.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s stack trace (with my patch applied):&lt;/p&gt;
&lt;p&gt;len &amp;gt;= 65536u
WARNING: ./include/linux/udp.h:38 at udp_set_len_short include/linux/udp.h:38 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:132…&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;l2tp: Drop large packets with UDP encap&lt;/p&gt;
&lt;p&gt;syzbot reported a WARN on my patch series [1]. The actual issue is an
overflow of 16-bit UDP length field, and it exists in the upstream code.
My series added a debug WARN with an overflow check that exposed the
issue, that&amp;#39;s why syzbot tripped on my patches, rather than on upstream
code.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s repro:&lt;/p&gt;
&lt;p&gt;r0 = socket$pppl2tp(0x18, 0x1, 0x1)
r1 = socket$inet6_udp(0xa, 0x2, 0x0)
connect$inet6(r1, &amp;amp;(0x7f00000000c0)={0xa, 0x0, 0x0, @loopback, 0xfffffffc}, 0x1c)
connect$pppl2tp(r0, &amp;amp;(0x7f0000000240)=@pppol2tpin6={0x18, 0x1, {0x0, r1, 0x4, 0x0, 0x0, 0x0, {0xa, 0x4e22, 0xffff, @ipv4={&amp;#39;\x00&amp;#39;, &amp;#39;\xff\xff&amp;#39;, @empty}}}}, 0x32)
writev(r0, &amp;amp;(0x7f0000000080)=[{&amp;amp;(0x7f0000000000)=&amp;#34;ee&amp;#34;, 0x34000}], 0x1)&lt;/p&gt;
&lt;p&gt;It basically sends an oversized (0x34000 bytes) PPPoL2TP packet with UDP
encapsulation, and l2tp_xmit_core doesn&amp;#39;t check for overflows when it
assigns the UDP length field. The value gets trimmed to 16 bites.&lt;/p&gt;
&lt;p&gt;Add an overflow check that drops oversized packets and avoids sending
packets with trimmed UDP length to the wire.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s stack trace (with my patch applied):&lt;/p&gt;
&lt;p&gt;len &amp;gt;= 65536u
WARNING: ./include/linux/udp.h:38 at udp_set_len_short include/linux/udp.h:38 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:132…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-43080</guid>
    </item>
    <item>
      <title>GHSA-pmcg-f5m4-2gwp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pmcg-f5m4-2gwp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;l2tp: Drop large packets with UDP encap&lt;/p&gt;
&lt;p&gt;syzbot reported a WARN on my patch series [1]. The actual issue is an
overflow of 16-bit UDP length field, and it exists in the upstream code.
My series added a debug WARN with an overflow check that exposed the
issue, that&amp;#39;s why syzbot tripped on my patches, rather than on upstream
code.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s repro:&lt;/p&gt;
&lt;p&gt;r0 = socket$pppl2tp(0x18, 0x1, 0x1)
r1 = socket$inet6_udp(0xa, 0x2, 0x0)
connect$inet6(r1, &amp;amp;(0x7f00000000c0)={0xa, 0x0, 0x0, @loopback, 0xfffffffc}, 0x1c)
connect$pppl2tp(r0, &amp;amp;(0x7f0000000240)=@pppol2tpin6={0x18, 0x1, {0x0, r1, 0x4, 0x0, 0x0, 0x0, {0xa, 0x4e22, 0xffff, @ipv4={&amp;#39;\x00&amp;#39;, &amp;#39;\xff\xff&amp;#39;, @empty}}}}, 0x32)
writev(r0, &amp;amp;(0x7f0000000080)=[{&amp;amp;(0x7f0000000000)=&amp;#34;ee&amp;#34;, 0x34000}], 0x1)&lt;/p&gt;
&lt;p&gt;It basically sends an oversized (0x34000 bytes) PPPoL2TP packet with UDP
encapsulation, and l2tp_xmit_core doesn&amp;#39;t check for overflows when it
assigns the UDP length field. The value gets trimmed to 16 bites.&lt;/p&gt;
&lt;p&gt;Add an overflow check that drops oversized packets and avoids sending
packets with trimmed UDP length to the wire.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s stack trace (with my patch applied):&lt;/p&gt;
&lt;p&gt;len &amp;gt;= 65536u
WARNING: ./include/linux/udp.h:38 at udp_set_len_short include/linux/udp.h:38 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:132…&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;l2tp: Drop large packets with UDP encap&lt;/p&gt;
&lt;p&gt;syzbot reported a WARN on my patch series [1]. The actual issue is an
overflow of 16-bit UDP length field, and it exists in the upstream code.
My series added a debug WARN with an overflow check that exposed the
issue, that&amp;#39;s why syzbot tripped on my patches, rather than on upstream
code.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s repro:&lt;/p&gt;
&lt;p&gt;r0 = socket$pppl2tp(0x18, 0x1, 0x1)
r1 = socket$inet6_udp(0xa, 0x2, 0x0)
connect$inet6(r1, &amp;amp;(0x7f00000000c0)={0xa, 0x0, 0x0, @loopback, 0xfffffffc}, 0x1c)
connect$pppl2tp(r0, &amp;amp;(0x7f0000000240)=@pppol2tpin6={0x18, 0x1, {0x0, r1, 0x4, 0x0, 0x0, 0x0, {0xa, 0x4e22, 0xffff, @ipv4={&amp;#39;\x00&amp;#39;, &amp;#39;\xff\xff&amp;#39;, @empty}}}}, 0x32)
writev(r0, &amp;amp;(0x7f0000000080)=[{&amp;amp;(0x7f0000000000)=&amp;#34;ee&amp;#34;, 0x34000}], 0x1)&lt;/p&gt;
&lt;p&gt;It basically sends an oversized (0x34000 bytes) PPPoL2TP packet with UDP
encapsulation, and l2tp_xmit_core doesn&amp;#39;t check for overflows when it
assigns the UDP length field. The value gets trimmed to 16 bites.&lt;/p&gt;
&lt;p&gt;Add an overflow check that drops oversized packets and avoids sending
packets with trimmed UDP length to the wire.&lt;/p&gt;
&lt;p&gt;syzbot&amp;#39;s stack trace (with my patch applied):&lt;/p&gt;
&lt;p&gt;len &amp;gt;= 65536u
WARNING: ./include/linux/udp.h:38 at udp_set_len_short include/linux/udp.h:38 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline], CPU#1: syz.0.17/5957
WARNING: ./include/linux/udp.h:38 at l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:132…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pmcg-f5m4-2gwp</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21388-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21388-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:21388-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22521-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22521-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:22521-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43080</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43080</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 233 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: l2tp: Drop large packets with UDP encap syzbot reported a WARN on my patch series [1]. The actual issue is an overflow of 16-bit UDP length field, and it exists in the upstream code. My series added a debug WARN with an overflow check that exposed the issue, that&amp;#39;s why syzbot tripped on my patches, rather than on upstream code. syzbot&amp;#39;s repro: r0 = socket$pppl2tp(0x18, 0x1, 0x1) r1 = socket$inet6_udp(0xa, 0x2, 0x0) connect$inet6(r1, &amp;amp;(0x7f00000000c0)={0xa, 0x0, 0x0, @loopback, 0xfffffffc}, 0x1c) connect$pppl2tp(r0, &amp;amp;(0x7f0000000240)=@pppol2tpin6={0x18, 0x1, {0x0, r1, 0x4, 0x0, 0x0, 0x0, {0xa, 0x4e22, 0xffff, @ipv4={&amp;#39;\x00&amp;#39;, &amp;#39;\xff\xff&amp;#39;, @empty}}}}, 0x32) writev(r0, &amp;amp;(0x7f0000000080)=[{&amp;amp;(0x7f0000000000)=&amp;#34;ee&amp;#34;, 0x34000}], 0x1) It basically sends an oversized (0x34000 bytes) PPPoL2TP packet with UDP encapsulation, and l2tp_xmit_core doesn&amp;#39;t check for overflows when it assigns the UDP length field. The value gets trimmed to 16 bites. Add an overflow check that drops oversized packets and avoids sending packets with trimmed UDP length to the wire. syzbot&amp;#39;s stack trace (with my patch applied): len &amp;gt;= 65536u WARNING: ./include/linux/udp.h:38 at udp_set_len_short include/linux/udp.h:38 [inline], CPU#1: syz.0.17/5957 WARNING: ./include/linux/udp.h:38 at l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline], CPU#1: syz.0.17/5957 WARNING: ./include/linux/udp.h:38 at l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:1327, CPU#1…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 233 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: l2tp: Drop large packets with UDP encap syzbot reported a WARN on my patch series [1]. The actual issue is an overflow of 16-bit UDP length field, and it exists in the upstream code. My series added a debug WARN with an overflow check that exposed the issue, that&amp;#39;s why syzbot tripped on my patches, rather than on upstream code. syzbot&amp;#39;s repro: r0 = socket$pppl2tp(0x18, 0x1, 0x1) r1 = socket$inet6_udp(0xa, 0x2, 0x0) connect$inet6(r1, &amp;amp;(0x7f00000000c0)={0xa, 0x0, 0x0, @loopback, 0xfffffffc}, 0x1c) connect$pppl2tp(r0, &amp;amp;(0x7f0000000240)=@pppol2tpin6={0x18, 0x1, {0x0, r1, 0x4, 0x0, 0x0, 0x0, {0xa, 0x4e22, 0xffff, @ipv4={&amp;#39;\x00&amp;#39;, &amp;#39;\xff\xff&amp;#39;, @empty}}}}, 0x32) writev(r0, &amp;amp;(0x7f0000000080)=[{&amp;amp;(0x7f0000000000)=&amp;#34;ee&amp;#34;, 0x34000}], 0x1) It basically sends an oversized (0x34000 bytes) PPPoL2TP packet with UDP encapsulation, and l2tp_xmit_core doesn&amp;#39;t check for overflows when it assigns the UDP length field. The value gets trimmed to 16 bites. Add an overflow check that drops oversized packets and avoids sending packets with trimmed UDP length to the wire. syzbot&amp;#39;s stack trace (with my patch applied): len &amp;gt;= 65536u WARNING: ./include/linux/udp.h:38 at udp_set_len_short include/linux/udp.h:38 [inline], CPU#1: syz.0.17/5957 WARNING: ./include/linux/udp.h:38 at l2tp_xmit_core net/l2tp/l2tp_core.c:1293 [inline], CPU#1: syz.0.17/5957 WARNING: ./include/linux/udp.h:38 at l2tp_xmit_skb+0x1204/0x18d0 net/l2tp/l2tp_core.c:1327, CPU#1…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-43080</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1385 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1385</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1385</guid>
    </item>
  </channel>
</rss>
