<?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, 04 Oct 2026 06:55:33 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-13882</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-13882</link>
      <description>bdu:2025-13882</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-13882</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-39850</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-39850</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-39850</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0825 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</link>
      <description>certfr-2025-avi-0825</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0825</guid>
    </item>
    <item>
      <title>EUVD-2026-314789</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-314789</link>
      <description>EUVD-2026-314789</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-314789</guid>
    </item>
    <item>
      <title>fkie_cve-2025-39850</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-39850</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects&lt;/p&gt;
&lt;p&gt;When the &amp;#34;proxy&amp;#34; option is enabled on a VXLAN device, the device will
suppress ARP requests and IPv6 Neighbor Solicitation messages if it is
able to reply on behalf of the remote host. That is, if a matching and
valid neighbor entry is configured on the VXLAN device whose MAC address
is not behind the &amp;#34;any&amp;#34; remote (0.0.0.0 / ::).&lt;/p&gt;
&lt;p&gt;The code currently assumes that the FDB entry for the neighbor&amp;#39;s MAC
address points to a valid remote destination, but this is incorrect if
the entry is associated with an FDB nexthop group. This can result in a
NPD [1][3] which can be reproduced using [2][4].&lt;/p&gt;
&lt;p&gt;Fix by checking that the remote destination exists before dereferencing
it.&lt;/p&gt;
&lt;p&gt;[1]
BUG: kernel NULL pointer dereference, address: 0000000000000000
[...]
CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014
RIP: 0010:vxlan_xmit+0xb58/0x15f0
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 dev_hard_start_xmit+0x5d/0x1c0
 __dev_queue_xmit+0x246/0xfd0
 packet_sendmsg+0x113a/0x1850
 __sock_sendmsg+0x38/0x70
 __sys_sendto+0x126/0x180
 __x64_sys_sendto+0x24/0x30
 do_syscall_64+0xa4/0x260
 entry_SYSCALL_64_after_hwframe+0x4b/0x53&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;ip address add 192.0.2.1/32 dev lo&lt;/p&gt;
&lt;p&gt;ip nexthop add id 1 via 192.0.2.2 fdb
 ip nexthop add id 10 group 1 fdb…&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;vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects&lt;/p&gt;
&lt;p&gt;When the &amp;#34;proxy&amp;#34; option is enabled on a VXLAN device, the device will
suppress ARP requests and IPv6 Neighbor Solicitation messages if it is
able to reply on behalf of the remote host. That is, if a matching and
valid neighbor entry is configured on the VXLAN device whose MAC address
is not behind the &amp;#34;any&amp;#34; remote (0.0.0.0 / ::).&lt;/p&gt;
&lt;p&gt;The code currently assumes that the FDB entry for the neighbor&amp;#39;s MAC
address points to a valid remote destination, but this is incorrect if
the entry is associated with an FDB nexthop group. This can result in a
NPD [1][3] which can be reproduced using [2][4].&lt;/p&gt;
&lt;p&gt;Fix by checking that the remote destination exists before dereferencing
it.&lt;/p&gt;
&lt;p&gt;[1]
BUG: kernel NULL pointer dereference, address: 0000000000000000
[...]
CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014
RIP: 0010:vxlan_xmit+0xb58/0x15f0
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 dev_hard_start_xmit+0x5d/0x1c0
 __dev_queue_xmit+0x246/0xfd0
 packet_sendmsg+0x113a/0x1850
 __sock_sendmsg+0x38/0x70
 __sys_sendto+0x126/0x180
 __x64_sys_sendto+0x24/0x30
 do_syscall_64+0xa4/0x260
 entry_SYSCALL_64_after_hwframe+0x4b/0x53&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;ip address add 192.0.2.1/32 dev lo&lt;/p&gt;
&lt;p&gt;ip nexthop add id 1 via 192.0.2.2 fdb
 ip nexthop add id 10 group 1 fdb…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-39850</guid>
    </item>
    <item>
      <title>GHSA-53q5-cxhh-w27r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-53q5-cxhh-w27r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects&lt;/p&gt;
&lt;p&gt;When the &amp;#34;proxy&amp;#34; option is enabled on a VXLAN device, the device will
suppress ARP requests and IPv6 Neighbor Solicitation messages if it is
able to reply on behalf of the remote host. That is, if a matching and
valid neighbor entry is configured on the VXLAN device whose MAC address
is not behind the &amp;#34;any&amp;#34; remote (0.0.0.0 / ::).&lt;/p&gt;
&lt;p&gt;The code currently assumes that the FDB entry for the neighbor&amp;#39;s MAC
address points to a valid remote destination, but this is incorrect if
the entry is associated with an FDB nexthop group. This can result in a
NPD [1][3] which can be reproduced using [2][4].&lt;/p&gt;
&lt;p&gt;Fix by checking that the remote destination exists before dereferencing
it.&lt;/p&gt;
&lt;p&gt;[1]
BUG: kernel NULL pointer dereference, address: 0000000000000000
[...]
CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014
RIP: 0010:vxlan_xmit+0xb58/0x15f0
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 dev_hard_start_xmit+0x5d/0x1c0
 __dev_queue_xmit+0x246/0xfd0
 packet_sendmsg+0x113a/0x1850
 __sock_sendmsg+0x38/0x70
 __sys_sendto+0x126/0x180
 __x64_sys_sendto+0x24/0x30
 do_syscall_64+0xa4/0x260
 entry_SYSCALL_64_after_hwframe+0x4b/0x53&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;ip address add 192.0.2.1/32 dev lo&lt;/p&gt;
&lt;p&gt;ip nexthop add id 1 via 192.0.2.2 fdb
 ip nexthop add id 10 group 1 fdb…&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;vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects&lt;/p&gt;
&lt;p&gt;When the &amp;#34;proxy&amp;#34; option is enabled on a VXLAN device, the device will
suppress ARP requests and IPv6 Neighbor Solicitation messages if it is
able to reply on behalf of the remote host. That is, if a matching and
valid neighbor entry is configured on the VXLAN device whose MAC address
is not behind the &amp;#34;any&amp;#34; remote (0.0.0.0 / ::).&lt;/p&gt;
&lt;p&gt;The code currently assumes that the FDB entry for the neighbor&amp;#39;s MAC
address points to a valid remote destination, but this is incorrect if
the entry is associated with an FDB nexthop group. This can result in a
NPD [1][3] which can be reproduced using [2][4].&lt;/p&gt;
&lt;p&gt;Fix by checking that the remote destination exists before dereferencing
it.&lt;/p&gt;
&lt;p&gt;[1]
BUG: kernel NULL pointer dereference, address: 0000000000000000
[...]
CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary)
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014
RIP: 0010:vxlan_xmit+0xb58/0x15f0
[...]
Call Trace:
 &amp;lt;TASK&amp;gt;
 dev_hard_start_xmit+0x5d/0x1c0
 __dev_queue_xmit+0x246/0xfd0
 packet_sendmsg+0x113a/0x1850
 __sock_sendmsg+0x38/0x70
 __sys_sendto+0x126/0x180
 __x64_sys_sendto+0x24/0x30
 do_syscall_64+0xa4/0x260
 entry_SYSCALL_64_after_hwframe+0x4b/0x53&lt;/p&gt;
&lt;p&gt;[2]
 #!/bin/bash&lt;/p&gt;
&lt;p&gt;ip address add 192.0.2.1/32 dev lo&lt;/p&gt;
&lt;p&gt;ip nexthop add id 1 via 192.0.2.2 fdb
 ip nexthop add id 10 group 1 fdb…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-53q5-cxhh-w27r</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-39850 — vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-39850</link>
      <description>msrc_CVE-2025-39850</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-39850</guid>
    </item>
    <item>
      <title>OESA-2025-2465 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2465</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;Bluetooth: hci_conn: Use disable_delayed_work_sync&lt;/p&gt;
&lt;p&gt;This makes use of disable_delayed_work_sync instead
cancel_delayed_work_sync as it not only cancel the ongoing work but also
disables new submit which is disarable since the object holding the work
is about to be freed.(CVE-2024-56591)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().&lt;/p&gt;
&lt;p&gt;fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.&lt;/p&gt;
&lt;p&gt;Commit 7dd73168e273 (&amp;amp;quot;ipv6: Always allocate pcpu memory in a fib6_nh&amp;amp;quot;)
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh-&amp;amp;gt;nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh-&amp;amp;gt;rt6i_pcpu, resulting in memleak.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.&lt;/p&gt;
&lt;p&gt;Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.(CVE-2025-22005)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Fix a couple integer overflows on 32bit systems&lt;/p&gt;
&lt;p&gt;On 32bit systems the &amp;amp;quot;off + sizeof(struct NTFS_DE)&amp;amp;quot; addition can
have an integer wrapping issue.  Fix it by using size_add().(CVE-2025-22081)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been re…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;Bluetooth: hci_conn: Use disable_delayed_work_sync&lt;/p&gt;
&lt;p&gt;This makes use of disable_delayed_work_sync instead
cancel_delayed_work_sync as it not only cancel the ongoing work but also
disables new submit which is disarable since the object holding the work
is about to be freed.(CVE-2024-56591)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ipv6: Fix memleak of nhc_pcpu_rth_output in fib_check_nh_v6_gw().&lt;/p&gt;
&lt;p&gt;fib_check_nh_v6_gw() expects that fib6_nh_init() cleans up everything
when it fails.&lt;/p&gt;
&lt;p&gt;Commit 7dd73168e273 (&amp;amp;quot;ipv6: Always allocate pcpu memory in a fib6_nh&amp;amp;quot;)
moved fib_nh_common_init() before alloc_percpu_gfp() within fib6_nh_init()
but forgot to add cleanup for fib6_nh-&amp;amp;gt;nh_common.nhc_pcpu_rth_output in
case it fails to allocate fib6_nh-&amp;amp;gt;rt6i_pcpu, resulting in memleak.&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s call fib_nh_common_release() and clear nhc_pcpu_rth_output in the
error path.&lt;/p&gt;
&lt;p&gt;Note that we can remove the fib6_nh_release() call in nh_create_ipv6()
later in net-next.git.(CVE-2025-22005)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/ntfs3: Fix a couple integer overflows on 32bit systems&lt;/p&gt;
&lt;p&gt;On 32bit systems the &amp;amp;quot;off + sizeof(struct NTFS_DE)&amp;amp;quot; addition can
have an integer wrapping issue.  Fix it by using size_add().(CVE-2025-22081)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been re…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2465</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-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-2025:20081-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03600-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:03600-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-2025:03600-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39850</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39850</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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects When the &amp;#34;proxy&amp;#34; option is enabled on a VXLAN device, the device will suppress ARP requests and IPv6 Neighbor Solicitation messages if it is able to reply on behalf of the remote host. That is, if a matching and valid neighbor entry is configured on the VXLAN device whose MAC address is not behind the &amp;#34;any&amp;#34; remote (0.0.0.0 / ::). The code currently assumes that the FDB entry for the neighbor&amp;#39;s MAC address points to a valid remote destination, but this is incorrect if the entry is associated with an FDB nexthop group. This can result in a NPD [1][3] which can be reproduced using [2][4]. Fix by checking that the remote destination exists before dereferencing it. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 [...] CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 RIP: 0010:vxlan_xmit+0xb58/0x15f0 [...] Call Trace:  &amp;lt;TASK&amp;gt;  dev_hard_start_xmit+0x5d/0x1c0  __dev_queue_xmit+0x246/0xfd0  packet_sendmsg+0x113a/0x1850  __sock_sendmsg+0x38/0x70  __sys_sendto+0x126/0x180  __x64_sys_sendto+0x24/0x30  do_syscall_64+0xa4/0x260  entry_SYSCALL_64_after_hwframe+0x4b/0x53 [2]  #!/bin/bash  ip address add 192.0.2.1/32 dev lo  ip nexthop add id 1 via 192.0.2.2 fdb  ip nexthop add id 10 group 1 fdb  ip link…&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 163 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects When the &amp;#34;proxy&amp;#34; option is enabled on a VXLAN device, the device will suppress ARP requests and IPv6 Neighbor Solicitation messages if it is able to reply on behalf of the remote host. That is, if a matching and valid neighbor entry is configured on the VXLAN device whose MAC address is not behind the &amp;#34;any&amp;#34; remote (0.0.0.0 / ::). The code currently assumes that the FDB entry for the neighbor&amp;#39;s MAC address points to a valid remote destination, but this is incorrect if the entry is associated with an FDB nexthop group. This can result in a NPD [1][3] which can be reproduced using [2][4]. Fix by checking that the remote destination exists before dereferencing it. [1] BUG: kernel NULL pointer dereference, address: 0000000000000000 [...] CPU: 4 UID: 0 PID: 365 Comm: arping Not tainted 6.17.0-rc2-virtme-g2a89cb21162c #2 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-4.fc41 04/01/2014 RIP: 0010:vxlan_xmit+0xb58/0x15f0 [...] Call Trace:  &amp;lt;TASK&amp;gt;  dev_hard_start_xmit+0x5d/0x1c0  __dev_queue_xmit+0x246/0xfd0  packet_sendmsg+0x113a/0x1850  __sock_sendmsg+0x38/0x70  __sys_sendto+0x126/0x180  __x64_sys_sendto+0x24/0x30  do_syscall_64+0xa4/0x260  entry_SYSCALL_64_after_hwframe+0x4b/0x53 [2]  #!/bin/bash  ip address add 192.0.2.1/32 dev lo  ip nexthop add id 1 via 192.0.2.2 fdb  ip nexthop add id 10 group 1 fdb  ip link…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-39850</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2099 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2099</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2099</guid>
    </item>
  </channel>
</rss>
