<?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>Sun, 18 Oct 2026 23:49:50 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04001</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04001</link>
      <description>bdu:2026-04001</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04001</guid>
    </item>
    <item>
      <title>certfr-2025-avi-1057 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</link>
      <description>certfr-2025-avi-1057</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057</guid>
    </item>
    <item>
      <title>EUVD-2026-340628</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-340628</link>
      <description>EUVD-2026-340628</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-340628</guid>
    </item>
    <item>
      <title>fkie_cve-2022-49662</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-49662</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: fix lockdep splat in in6_dump_addrs()&lt;/p&gt;
&lt;p&gt;As reported by syzbot, we should not use rcu_dereference()
when rcu_read_lock() is not held.&lt;/p&gt;
&lt;p&gt;WARNING: suspicious RCU usage
5.19.0-rc2-syzkaller #0 Not tainted&lt;/p&gt;
&lt;p&gt;net/ipv6/addrconf.c:5175 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-executor326/3617:
 #0: ffffffff8d5848e8 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xae/0xc20 net/netlink/af_netlink.c:2223&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 0 PID: 3617 Comm: syz-executor326 Not tainted 5.19.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 in6_dump_addrs+0x12d1/0x1790 net/ipv6/addrconf.c:5175
 inet6_dump_addr+0x9c1/0xb50 net/ipv6/addrconf.c:5300
 netlink_dump+0x541/0xc20 net/netlink/af_netlink.c:2275
 __netlink_dump_start+0x647/0x900 net/netlink/af_netlink.c:2380
 netlink_dump_start include/linux/netlink.h:245 [inline]
 rtnetlink_rcv_msg+0x73e/0xc90 net/core/rtnetlink.c:6046
 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501
 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
 netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345
 netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921
 sock_sendmsg_nosec net/socket.c:714 [inline]
 sock…&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: fix lockdep splat in in6_dump_addrs()&lt;/p&gt;
&lt;p&gt;As reported by syzbot, we should not use rcu_dereference()
when rcu_read_lock() is not held.&lt;/p&gt;
&lt;p&gt;WARNING: suspicious RCU usage
5.19.0-rc2-syzkaller #0 Not tainted&lt;/p&gt;
&lt;p&gt;net/ipv6/addrconf.c:5175 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-executor326/3617:
 #0: ffffffff8d5848e8 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xae/0xc20 net/netlink/af_netlink.c:2223&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 0 PID: 3617 Comm: syz-executor326 Not tainted 5.19.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 in6_dump_addrs+0x12d1/0x1790 net/ipv6/addrconf.c:5175
 inet6_dump_addr+0x9c1/0xb50 net/ipv6/addrconf.c:5300
 netlink_dump+0x541/0xc20 net/netlink/af_netlink.c:2275
 __netlink_dump_start+0x647/0x900 net/netlink/af_netlink.c:2380
 netlink_dump_start include/linux/netlink.h:245 [inline]
 rtnetlink_rcv_msg+0x73e/0xc90 net/core/rtnetlink.c:6046
 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501
 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
 netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345
 netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921
 sock_sendmsg_nosec net/socket.c:714 [inline]
 sock…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-49662</guid>
    </item>
    <item>
      <title>GHSA-jpqg-mcww-p7pp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jpqg-mcww-p7pp</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: fix lockdep splat in in6_dump_addrs()&lt;/p&gt;
&lt;p&gt;As reported by syzbot, we should not use rcu_dereference()
when rcu_read_lock() is not held.&lt;/p&gt;
&lt;p&gt;WARNING: suspicious RCU usage
5.19.0-rc2-syzkaller #0 Not tainted&lt;/p&gt;
&lt;p&gt;net/ipv6/addrconf.c:5175 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-executor326/3617:
 #0: ffffffff8d5848e8 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xae/0xc20 net/netlink/af_netlink.c:2223&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 0 PID: 3617 Comm: syz-executor326 Not tainted 5.19.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 in6_dump_addrs+0x12d1/0x1790 net/ipv6/addrconf.c:5175
 inet6_dump_addr+0x9c1/0xb50 net/ipv6/addrconf.c:5300
 netlink_dump+0x541/0xc20 net/netlink/af_netlink.c:2275
 __netlink_dump_start+0x647/0x900 net/netlink/af_netlink.c:2380
 netlink_dump_start include/linux/netlink.h:245 [inline]
 rtnetlink_rcv_msg+0x73e/0xc90 net/core/rtnetlink.c:6046
 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501
 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
 netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345
 netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921
 sock_sendmsg_nosec net/socket.c:714 [inline]
 sock…&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: fix lockdep splat in in6_dump_addrs()&lt;/p&gt;
&lt;p&gt;As reported by syzbot, we should not use rcu_dereference()
when rcu_read_lock() is not held.&lt;/p&gt;
&lt;p&gt;WARNING: suspicious RCU usage
5.19.0-rc2-syzkaller #0 Not tainted&lt;/p&gt;
&lt;p&gt;net/ipv6/addrconf.c:5175 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-executor326/3617:
 #0: ffffffff8d5848e8 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xae/0xc20 net/netlink/af_netlink.c:2223&lt;/p&gt;
&lt;p&gt;stack backtrace:
CPU: 0 PID: 3617 Comm: syz-executor326 Not tainted 5.19.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 &amp;lt;TASK&amp;gt;
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
 in6_dump_addrs+0x12d1/0x1790 net/ipv6/addrconf.c:5175
 inet6_dump_addr+0x9c1/0xb50 net/ipv6/addrconf.c:5300
 netlink_dump+0x541/0xc20 net/netlink/af_netlink.c:2275
 __netlink_dump_start+0x647/0x900 net/netlink/af_netlink.c:2380
 netlink_dump_start include/linux/netlink.h:245 [inline]
 rtnetlink_rcv_msg+0x73e/0xc90 net/core/rtnetlink.c:6046
 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501
 netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]
 netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345
 netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921
 sock_sendmsg_nosec net/socket.c:714 [inline]
 sock…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jpqg-mcww-p7pp</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-49662</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49662</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 92 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: fix lockdep splat in in6_dump_addrs() As reported by syzbot, we should not use rcu_dereference() when rcu_read_lock() is not held. WARNING: suspicious RCU usage 5.19.0-rc2-syzkaller #0 Not tainted net/ipv6/addrconf.c:5175 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-executor326/3617:  #0: ffffffff8d5848e8 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xae/0xc20 net/netlink/af_netlink.c:2223 stack backtrace: CPU: 0 PID: 3617 Comm: syz-executor326 Not tainted 5.19.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106  in6_dump_addrs+0x12d1/0x1790 net/ipv6/addrconf.c:5175  inet6_dump_addr+0x9c1/0xb50 net/ipv6/addrconf.c:5300  netlink_dump+0x541/0xc20 net/netlink/af_netlink.c:2275  __netlink_dump_start+0x647/0x900 net/netlink/af_netlink.c:2380  netlink_dump_start include/linux/netlink.h:245 [inline]  rtnetlink_rcv_msg+0x73e/0xc90 net/core/rtnetlink.c:6046  netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501  netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]  netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345  netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921  sock_sendmsg_nosec net/socket.c:714 [inline]  sock_sendms…&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 92 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ipv6: fix lockdep splat in in6_dump_addrs() As reported by syzbot, we should not use rcu_dereference() when rcu_read_lock() is not held. WARNING: suspicious RCU usage 5.19.0-rc2-syzkaller #0 Not tainted net/ipv6/addrconf.c:5175 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-executor326/3617:  #0: ffffffff8d5848e8 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xae/0xc20 net/netlink/af_netlink.c:2223 stack backtrace: CPU: 0 PID: 3617 Comm: syz-executor326 Not tainted 5.19.0-rc2-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Call Trace:  &amp;lt;TASK&amp;gt;  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106  in6_dump_addrs+0x12d1/0x1790 net/ipv6/addrconf.c:5175  inet6_dump_addr+0x9c1/0xb50 net/ipv6/addrconf.c:5300  netlink_dump+0x541/0xc20 net/netlink/af_netlink.c:2275  __netlink_dump_start+0x647/0x900 net/netlink/af_netlink.c:2380  netlink_dump_start include/linux/netlink.h:245 [inline]  rtnetlink_rcv_msg+0x73e/0xc90 net/core/rtnetlink.c:6046  netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2501  netlink_unicast_kernel net/netlink/af_netlink.c:1319 [inline]  netlink_unicast+0x543/0x7f0 net/netlink/af_netlink.c:1345  netlink_sendmsg+0x917/0xe10 net/netlink/af_netlink.c:1921  sock_sendmsg_nosec net/socket.c:714 [inline]  sock_sendms…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-49662</guid>
    </item>
  </channel>
</rss>
