<?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>Tue, 06 Oct 2026 18:26:55 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-63984</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-63984</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-63984</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>EUVD-2026-348334</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-348334</link>
      <description>EUVD-2026-348334</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-348334</guid>
    </item>
    <item>
      <title>fkie_cve-2026-63984</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-63984</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress()&lt;/p&gt;
&lt;p&gt;ipv6_rpl_srh_decompress() computes:&lt;/p&gt;
&lt;p&gt;outhdr-&amp;gt;hdrlen = (((n + 1) * sizeof(struct in6_addr)) &amp;gt;&amp;gt; 3);&lt;/p&gt;
&lt;p&gt;hdrlen is __u8. For n &amp;gt;= 127 the result exceeds 255 and silently
truncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16):&lt;/p&gt;
&lt;p&gt;(128 * 16) &amp;gt;&amp;gt; 3 = 256, truncated to 0 as __u8&lt;/p&gt;
&lt;p&gt;The caller in ipv6_rpl_srh_rcv() then places the compressed header
at buf + ((ohdr-&amp;gt;hdrlen + 1) &amp;lt;&amp;lt; 3). With hdrlen=0 this is buf + 8,
but the decompressed region occupies buf[0..2055] (8-byte header
plus 128 full addresses). The compressed header overlaps the
decompressed data, and ipv6_rpl_srh_compress() writes into this
overlap, corrupting the routing header of the forwarded packet.&lt;/p&gt;
&lt;p&gt;The existing guard at exthdrs.c:546 checks (n + 1) &amp;gt; 255, which
prevents n+1 from overflowing unsigned char (the segments_left
field), but does not prevent the computed hdrlen from overflowing
__u8. n=127 passes because 128 &amp;lt;= 255, yet hdrlen=256 does not
fit.&lt;/p&gt;
&lt;p&gt;Tighten the bound to (n + 1) &amp;gt; 127. This caps n at 126, giving
hdrlen = (127 * 16) &amp;gt;&amp;gt; 3 = 254, which fits in __u8. The compressed
header then lands at buf + ((254 + 1) &amp;lt;&amp;lt; 3) = buf + 2040, exactly
past the decompressed region (buf[0..2039]). No overlap. 127
segments is well beyond any realistic RPL deployment.&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;ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress()&lt;/p&gt;
&lt;p&gt;ipv6_rpl_srh_decompress() computes:&lt;/p&gt;
&lt;p&gt;outhdr-&amp;gt;hdrlen = (((n + 1) * sizeof(struct in6_addr)) &amp;gt;&amp;gt; 3);&lt;/p&gt;
&lt;p&gt;hdrlen is __u8. For n &amp;gt;= 127 the result exceeds 255 and silently
truncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16):&lt;/p&gt;
&lt;p&gt;(128 * 16) &amp;gt;&amp;gt; 3 = 256, truncated to 0 as __u8&lt;/p&gt;
&lt;p&gt;The caller in ipv6_rpl_srh_rcv() then places the compressed header
at buf + ((ohdr-&amp;gt;hdrlen + 1) &amp;lt;&amp;lt; 3). With hdrlen=0 this is buf + 8,
but the decompressed region occupies buf[0..2055] (8-byte header
plus 128 full addresses). The compressed header overlaps the
decompressed data, and ipv6_rpl_srh_compress() writes into this
overlap, corrupting the routing header of the forwarded packet.&lt;/p&gt;
&lt;p&gt;The existing guard at exthdrs.c:546 checks (n + 1) &amp;gt; 255, which
prevents n+1 from overflowing unsigned char (the segments_left
field), but does not prevent the computed hdrlen from overflowing
__u8. n=127 passes because 128 &amp;lt;= 255, yet hdrlen=256 does not
fit.&lt;/p&gt;
&lt;p&gt;Tighten the bound to (n + 1) &amp;gt; 127. This caps n at 126, giving
hdrlen = (127 * 16) &amp;gt;&amp;gt; 3 = 254, which fits in __u8. The compressed
header then lands at buf + ((254 + 1) &amp;lt;&amp;lt; 3) = buf + 2040, exactly
past the decompressed region (buf[0..2039]). No overlap. 127
segments is well beyond any realistic RPL deployment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-63984</guid>
    </item>
    <item>
      <title>GHSA-6hh9-w4p2-c5qm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6hh9-w4p2-c5qm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress()&lt;/p&gt;
&lt;p&gt;ipv6_rpl_srh_decompress() computes:&lt;/p&gt;
&lt;p&gt;outhdr-&amp;gt;hdrlen = (((n + 1) * sizeof(struct in6_addr)) &amp;gt;&amp;gt; 3);&lt;/p&gt;
&lt;p&gt;hdrlen is __u8. For n &amp;gt;= 127 the result exceeds 255 and silently
truncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16):&lt;/p&gt;
&lt;p&gt;(128 * 16) &amp;gt;&amp;gt; 3 = 256, truncated to 0 as __u8&lt;/p&gt;
&lt;p&gt;The caller in ipv6_rpl_srh_rcv() then places the compressed header
at buf + ((ohdr-&amp;gt;hdrlen + 1) &amp;lt;&amp;lt; 3). With hdrlen=0 this is buf + 8,
but the decompressed region occupies buf[0..2055] (8-byte header
plus 128 full addresses). The compressed header overlaps the
decompressed data, and ipv6_rpl_srh_compress() writes into this
overlap, corrupting the routing header of the forwarded packet.&lt;/p&gt;
&lt;p&gt;The existing guard at exthdrs.c:546 checks (n + 1) &amp;gt; 255, which
prevents n+1 from overflowing unsigned char (the segments_left
field), but does not prevent the computed hdrlen from overflowing
__u8. n=127 passes because 128 &amp;lt;= 255, yet hdrlen=256 does not
fit.&lt;/p&gt;
&lt;p&gt;Tighten the bound to (n + 1) &amp;gt; 127. This caps n at 126, giving
hdrlen = (127 * 16) &amp;gt;&amp;gt; 3 = 254, which fits in __u8. The compressed
header then lands at buf + ((254 + 1) &amp;lt;&amp;lt; 3) = buf + 2040, exactly
past the decompressed region (buf[0..2039]). No overlap. 127
segments is well beyond any realistic RPL deployment.&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;ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress()&lt;/p&gt;
&lt;p&gt;ipv6_rpl_srh_decompress() computes:&lt;/p&gt;
&lt;p&gt;outhdr-&amp;gt;hdrlen = (((n + 1) * sizeof(struct in6_addr)) &amp;gt;&amp;gt; 3);&lt;/p&gt;
&lt;p&gt;hdrlen is __u8. For n &amp;gt;= 127 the result exceeds 255 and silently
truncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16):&lt;/p&gt;
&lt;p&gt;(128 * 16) &amp;gt;&amp;gt; 3 = 256, truncated to 0 as __u8&lt;/p&gt;
&lt;p&gt;The caller in ipv6_rpl_srh_rcv() then places the compressed header
at buf + ((ohdr-&amp;gt;hdrlen + 1) &amp;lt;&amp;lt; 3). With hdrlen=0 this is buf + 8,
but the decompressed region occupies buf[0..2055] (8-byte header
plus 128 full addresses). The compressed header overlaps the
decompressed data, and ipv6_rpl_srh_compress() writes into this
overlap, corrupting the routing header of the forwarded packet.&lt;/p&gt;
&lt;p&gt;The existing guard at exthdrs.c:546 checks (n + 1) &amp;gt; 255, which
prevents n+1 from overflowing unsigned char (the segments_left
field), but does not prevent the computed hdrlen from overflowing
__u8. n=127 passes because 128 &amp;lt;= 255, yet hdrlen=256 does not
fit.&lt;/p&gt;
&lt;p&gt;Tighten the bound to (n + 1) &amp;gt; 127. This caps n at 126, giving
hdrlen = (127 * 16) &amp;gt;&amp;gt; 3 = 254, which fits in __u8. The compressed
header then lands at buf + ((254 + 1) &amp;lt;&amp;lt; 3) = buf + 2040, exactly
past the decompressed region (buf[0..2039]). No overlap. 127
segments is well beyond any realistic RPL deployment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6hh9-w4p2-c5qm</guid>
    </item>
    <item>
      <title>OESA-2026-3453 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-3453</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: cfg80211: cancel rfkill_block work in wiphy_unregister()&lt;/p&gt;
&lt;p&gt;There is a use-after-free error in cfg80211_shutdown_all_interfaces found
by syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in cfg80211_shutdown_all_interfaces+0x213/0x220
Read of size 8 at addr ffff888112a78d98 by task kworker/0:5/5326
CPU: 0 UID: 0 PID: 5326 Comm: kworker/0:5 Not tainted 6.19.0-rc2 #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
Workqueue: events cfg80211_rfkill_block_work
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 dump_stack_lvl+0x116/0x1f0
 print_report+0xcd/0x630
 kasan_report+0xe0/0x110
 cfg80211_shutdown_all_interfaces+0x213/0x220
 cfg80211_rfkill_block_work+0x1e/0x30
 process_one_work+0x9cf/0x1b70
 worker_thread+0x6c8/0xf10
 kthread+0x3c5/0x780
 ret_from_fork+0x56d/0x700
 ret_from_fork_asm+0x1a/0x30
 &amp;amp;lt;/TASK&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;The problem arises due to the rfkill_block work is not cancelled when wiphy
is being unregistered. In order to fix the issue cancel the corresponding
work in wiphy_unregister().&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2026-23336)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()&lt;/p&gt;
&lt;p&gt;l2cap_ecred_reconf_rsp() casts the incoming data to struct
l2cap_ecred_conn_rsp (the ECRED *connection* respons…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: cfg80211: cancel rfkill_block work in wiphy_unregister()&lt;/p&gt;
&lt;p&gt;There is a use-after-free error in cfg80211_shutdown_all_interfaces found
by syzkaller:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: use-after-free in cfg80211_shutdown_all_interfaces+0x213/0x220
Read of size 8 at addr ffff888112a78d98 by task kworker/0:5/5326
CPU: 0 UID: 0 PID: 5326 Comm: kworker/0:5 Not tainted 6.19.0-rc2 #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
Workqueue: events cfg80211_rfkill_block_work
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 dump_stack_lvl+0x116/0x1f0
 print_report+0xcd/0x630
 kasan_report+0xe0/0x110
 cfg80211_shutdown_all_interfaces+0x213/0x220
 cfg80211_rfkill_block_work+0x1e/0x30
 process_one_work+0x9cf/0x1b70
 worker_thread+0x6c8/0xf10
 kthread+0x3c5/0x780
 ret_from_fork+0x56d/0x700
 ret_from_fork_asm+0x1a/0x30
 &amp;amp;lt;/TASK&amp;amp;gt;&lt;/p&gt;
&lt;p&gt;The problem arises due to the rfkill_block work is not cancelled when wiphy
is being unregistered. In order to fix the issue cancel the corresponding
work in wiphy_unregister().&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with Syzkaller.(CVE-2026-23336)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()&lt;/p&gt;
&lt;p&gt;l2cap_ecred_reconf_rsp() casts the incoming data to struct
l2cap_ecred_conn_rsp (the ECRED *connection* respons…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-3453</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:23193-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:23193-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:23193-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63984</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63984</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 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() ipv6_rpl_srh_decompress() computes:     outhdr-&amp;gt;hdrlen = (((n + 1) * sizeof(struct in6_addr)) &amp;gt;&amp;gt; 3); hdrlen is __u8. For n &amp;gt;= 127 the result exceeds 255 and silently truncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16):     (128 * 16) &amp;gt;&amp;gt; 3 = 256, truncated to 0 as __u8 The caller in ipv6_rpl_srh_rcv() then places the compressed header at buf + ((ohdr-&amp;gt;hdrlen + 1) &amp;lt;&amp;lt; 3). With hdrlen=0 this is buf + 8, but the decompressed region occupies buf[0..2055] (8-byte header plus 128 full addresses). The compressed header overlaps the decompressed data, and ipv6_rpl_srh_compress() writes into this overlap, corrupting the routing header of the forwarded packet. The existing guard at exthdrs.c:546 checks (n + 1) &amp;gt; 255, which prevents n+1 from overflowing unsigned char (the segments_left field), but does not prevent the computed hdrlen from overflowing __u8. n=127 passes because 128 &amp;lt;= 255, yet hdrlen=256 does not fit. Tighten the bound to (n + 1) &amp;gt; 127. This caps n at 126, giving hdrlen = (127 * 16) &amp;gt;&amp;gt; 3 = 254, which fits in __u8. The compressed header then lands at buf + ((254 + 1) &amp;lt;&amp;lt; 3) = buf + 2040, exactly past the decompressed region (buf[0..2039]). No overlap. 127 segments is well beyond any realistic RPL deployment.&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 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() ipv6_rpl_srh_decompress() computes:     outhdr-&amp;gt;hdrlen = (((n + 1) * sizeof(struct in6_addr)) &amp;gt;&amp;gt; 3); hdrlen is __u8. For n &amp;gt;= 127 the result exceeds 255 and silently truncates. With n=127 (cmpri=15, cmpre=15, pad=0, hdrlen=16):     (128 * 16) &amp;gt;&amp;gt; 3 = 256, truncated to 0 as __u8 The caller in ipv6_rpl_srh_rcv() then places the compressed header at buf + ((ohdr-&amp;gt;hdrlen + 1) &amp;lt;&amp;lt; 3). With hdrlen=0 this is buf + 8, but the decompressed region occupies buf[0..2055] (8-byte header plus 128 full addresses). The compressed header overlaps the decompressed data, and ipv6_rpl_srh_compress() writes into this overlap, corrupting the routing header of the forwarded packet. The existing guard at exthdrs.c:546 checks (n + 1) &amp;gt; 255, which prevents n+1 from overflowing unsigned char (the segments_left field), but does not prevent the computed hdrlen from overflowing __u8. n=127 passes because 128 &amp;lt;= 255, yet hdrlen=256 does not fit. Tighten the bound to (n + 1) &amp;gt; 127. This caps n at 126, giving hdrlen = (127 * 16) &amp;gt;&amp;gt; 3 = 254, which fits in __u8. The compressed header then lands at buf + ((254 + 1) &amp;lt;&amp;lt; 3) = buf + 2040, exactly past the decompressed region (buf[0..2039]). No overlap. 127 segments is well beyond any realistic RPL deployment.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-63984</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2403 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&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, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2403</guid>
    </item>
  </channel>
</rss>
