<?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>Thu, 08 Oct 2026 03:31:46 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-10737</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-10737</link>
      <description>bdu:2025-10737</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-10737</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38324</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38324</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-2025-38324</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>EUVD-2026-314541</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314541</link>
      <description>EUVD-2026-314541</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314541</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38324</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38324</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().&lt;/p&gt;
&lt;p&gt;As syzbot reported [0], mpls_route_input_rcu() can be called
from mpls_getroute(), where is under RTNL.&lt;/p&gt;
&lt;p&gt;net-&amp;gt;mpls.platform_label is only updated under RTNL.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to
silence the splat.&lt;/p&gt;
&lt;p&gt;[0]:
WARNING: suspicious RCU usage
6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted
 ----------------------------
net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.2.4451/17730:
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120
 lockdep_rcu_suspicious+0x166/0x260 kernel/locking/lockdep.c:6865
 mpls_route_input_rcu+0x1d4/0x200 net/mpls/af_mpls.c:84
 mpls_getroute+0x621/0x1ea0 net/mpls/af_mpls.c:2381
 rtnetlink_rcv_msg+0x3c9/0xe90 net/core/rtnetlink.c:6964
 netlink_rcv_skb+0x16d/0x440 net/netlink/af_netlink.c:2534…&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;mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().&lt;/p&gt;
&lt;p&gt;As syzbot reported [0], mpls_route_input_rcu() can be called
from mpls_getroute(), where is under RTNL.&lt;/p&gt;
&lt;p&gt;net-&amp;gt;mpls.platform_label is only updated under RTNL.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to
silence the splat.&lt;/p&gt;
&lt;p&gt;[0]:
WARNING: suspicious RCU usage
6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted
 ----------------------------
net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.2.4451/17730:
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120
 lockdep_rcu_suspicious+0x166/0x260 kernel/locking/lockdep.c:6865
 mpls_route_input_rcu+0x1d4/0x200 net/mpls/af_mpls.c:84
 mpls_getroute+0x621/0x1ea0 net/mpls/af_mpls.c:2381
 rtnetlink_rcv_msg+0x3c9/0xe90 net/core/rtnetlink.c:6964
 netlink_rcv_skb+0x16d/0x440 net/netlink/af_netlink.c:2534…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38324</guid>
    </item>
    <item>
      <title>GHSA-94vx-8jmh-wjcj</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-94vx-8jmh-wjcj</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().&lt;/p&gt;
&lt;p&gt;As syzbot reported [0], mpls_route_input_rcu() can be called
from mpls_getroute(), where is under RTNL.&lt;/p&gt;
&lt;p&gt;net-&amp;gt;mpls.platform_label is only updated under RTNL.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to
silence the splat.&lt;/p&gt;
&lt;p&gt;[0]:
WARNING: suspicious RCU usage
6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted
 ----------------------------
net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.2.4451/17730:
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120
 lockdep_rcu_suspicious+0x166/0x260 kernel/locking/lockdep.c:6865
 mpls_route_input_rcu+0x1d4/0x200 net/mpls/af_mpls.c:84
 mpls_getroute+0x621/0x1ea0 net/mpls/af_mpls.c:2381
 rtnetlink_rcv_msg+0x3c9/0xe90 net/core/rtnetlink.c:6964
 netlink_rcv_skb+0x16d/0x440 net/netlink/af_netlink.c:2534…&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;mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().&lt;/p&gt;
&lt;p&gt;As syzbot reported [0], mpls_route_input_rcu() can be called
from mpls_getroute(), where is under RTNL.&lt;/p&gt;
&lt;p&gt;net-&amp;gt;mpls.platform_label is only updated under RTNL.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to
silence the splat.&lt;/p&gt;
&lt;p&gt;[0]:
WARNING: suspicious RCU usage
6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted
 ----------------------------
net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.2.4451/17730:
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120
 lockdep_rcu_suspicious+0x166/0x260 kernel/locking/lockdep.c:6865
 mpls_route_input_rcu+0x1d4/0x200 net/mpls/af_mpls.c:84
 mpls_getroute+0x621/0x1ea0 net/mpls/af_mpls.c:2381
 rtnetlink_rcv_msg+0x3c9/0xe90 net/core/rtnetlink.c:6964
 netlink_rcv_skb+0x16d/0x440 net/netlink/af_netlink.c:2534…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-94vx-8jmh-wjcj</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38324 — mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38324</link>
      <description>msrc_CVE-2025-38324</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38324</guid>
    </item>
    <item>
      <title>OESA-2025-1923 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1923</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;ipc: fix to protect IPCS lookups using RCU&lt;/p&gt;
&lt;p&gt;syzbot reported that it discovered a use-after-free vulnerability, [0]&lt;/p&gt;
&lt;p&gt;[0]: https://lore.kernel.org/all/(CVE-2025-38212)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().&lt;/p&gt;
&lt;p&gt;As syzbot reported [0], mpls_route_input_rcu() can be called
from mpls_getroute(), where is under RTNL.&lt;/p&gt;
&lt;p&gt;net-&amp;amp;gt;mpls.platform_label is only updated under RTNL.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to
silence the splat.&lt;/p&gt;
&lt;p&gt;[0]:
WARNING: suspicious RCU usage
6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted
 ----------------------------
net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.2.4451/17730:
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lv…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;ipc: fix to protect IPCS lookups using RCU&lt;/p&gt;
&lt;p&gt;syzbot reported that it discovered a use-after-free vulnerability, [0]&lt;/p&gt;
&lt;p&gt;[0]: https://lore.kernel.org/all/(CVE-2025-38212)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().&lt;/p&gt;
&lt;p&gt;As syzbot reported [0], mpls_route_input_rcu() can be called
from mpls_getroute(), where is under RTNL.&lt;/p&gt;
&lt;p&gt;net-&amp;amp;gt;mpls.platform_label is only updated under RTNL.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to
silence the splat.&lt;/p&gt;
&lt;p&gt;[0]:
WARNING: suspicious RCU usage
6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted
 ----------------------------
net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage!&lt;/p&gt;
&lt;p&gt;other info that might help us debug this:&lt;/p&gt;
&lt;p&gt;rcu_scheduler_active = 2, debug_locks = 1
1 lock held by syz.2.4451/17730:
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]
 #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
 &amp;amp;lt;TASK&amp;amp;gt;
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lv…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1923</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38324</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38324</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 213 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu(). As syzbot reported [0], mpls_route_input_rcu() can be called from mpls_getroute(), where is under RTNL. net-&amp;gt;mpls.platform_label is only updated under RTNL. Let&amp;#39;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to silence the splat. [0]: WARNING: suspicious RCU usage 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted  ---------------------------- net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.2.4451/17730:  #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]  #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961 stack backtrace: CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:94 [inline]  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120  lockdep_rcu_suspicious+0x166/0x260 kernel/locking/lockdep.c:6865  mpls_route_input_rcu+0x1d4/0x200 net/mpls/af_mpls.c:84  mpls_getroute+0x621/0x1ea0 net/mpls/af_mpls.c:2381  rtnetlink_rcv_msg+0x3c9/0xe90 net/core/rtnetlink.c:6964  netlink_rcv_skb+0x16d/0x440 net/netlink/af_netlink.c:2534  netlin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 213 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu(). As syzbot reported [0], mpls_route_input_rcu() can be called from mpls_getroute(), where is under RTNL. net-&amp;gt;mpls.platform_label is only updated under RTNL. Let&amp;#39;s use rcu_dereference_rtnl() in mpls_route_input_rcu() to silence the splat. [0]: WARNING: suspicious RCU usage 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted  ---------------------------- net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.2.4451/17730:  #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline]  #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961 stack backtrace: CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:94 [inline]  dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120  lockdep_rcu_suspicious+0x166/0x260 kernel/locking/lockdep.c:6865  mpls_route_input_rcu+0x1d4/0x200 net/mpls/af_mpls.c:84  mpls_getroute+0x621/0x1ea0 net/mpls/af_mpls.c:2381  rtnetlink_rcv_msg+0x3c9/0xe90 net/core/rtnetlink.c:6964  netlink_rcv_skb+0x16d/0x440 net/netlink/af_netlink.c:2534  netlin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38324</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1522 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1522</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1522</guid>
    </item>
  </channel>
</rss>
