<?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>Sat, 03 Oct 2026 07:12:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-11574</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-11574</link>
      <description>bdu:2024-11574</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-11574</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-38539</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-38539</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-38539</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0632 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0632</link>
      <description>certfr-2024-avi-0632</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0632</guid>
    </item>
    <item>
      <title>EUVD-2026-345801</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345801</link>
      <description>EUVD-2026-345801</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345801</guid>
    </item>
    <item>
      <title>fkie_cve-2024-38539</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-38539</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw&lt;/p&gt;
&lt;p&gt;When running blktests nvme/rdma, the following kmemleak issue will appear.&lt;/p&gt;
&lt;p&gt;kmemleak: Kernel memory leak detector initialized (mempool available:36041)
kmemleak: Automatic memory scanning thread started
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88855da53400 (size 192):
  comm &amp;#34;rdma&amp;#34;, pid 10630, jiffies 4296575922
  hex dump (first 32 bytes):
    37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00  7...............
    10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff  .4.].....4.]....
  backtrace (crc 47f66721):
    [&amp;lt;ffffffff911251bd&amp;gt;] kmalloc_trace+0x30d/0x3b0
    [&amp;lt;ffffffffc2640ff7&amp;gt;] alloc_gid_entry+0x47/0x380 [ib_core]
    [&amp;lt;ffffffffc2642206&amp;gt;] add_modify_gid+0x166/0x930 [ib_core]
    [&amp;lt;ffffffffc2643468&amp;gt;] ib_cache_update.part.0+0x6d8/0x910 [ib_core]
    [&amp;lt;ffffffffc2644e1a&amp;gt;] ib_cache_setup_one+0x24a/0x350 [ib_core]
    [&amp;lt;ffffffffc263949e&amp;gt;] ib_register_device+0x9e/0x3a0 [ib_core]
    [&amp;lt;ffffffffc2a3d389&amp;gt;] 0xffffffffc2a3d389
    [&amp;lt;ffffffffc2688cd8&amp;gt;] nldev_newlink+0x2b8/0x520 [ib_core]
    [&amp;lt;ffffffffc2645fe3&amp;gt;] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]
    [&amp;lt;ffffffffc26464…&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;RDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw&lt;/p&gt;
&lt;p&gt;When running blktests nvme/rdma, the following kmemleak issue will appear.&lt;/p&gt;
&lt;p&gt;kmemleak: Kernel memory leak detector initialized (mempool available:36041)
kmemleak: Automatic memory scanning thread started
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88855da53400 (size 192):
  comm &amp;#34;rdma&amp;#34;, pid 10630, jiffies 4296575922
  hex dump (first 32 bytes):
    37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00  7...............
    10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff  .4.].....4.]....
  backtrace (crc 47f66721):
    [&amp;lt;ffffffff911251bd&amp;gt;] kmalloc_trace+0x30d/0x3b0
    [&amp;lt;ffffffffc2640ff7&amp;gt;] alloc_gid_entry+0x47/0x380 [ib_core]
    [&amp;lt;ffffffffc2642206&amp;gt;] add_modify_gid+0x166/0x930 [ib_core]
    [&amp;lt;ffffffffc2643468&amp;gt;] ib_cache_update.part.0+0x6d8/0x910 [ib_core]
    [&amp;lt;ffffffffc2644e1a&amp;gt;] ib_cache_setup_one+0x24a/0x350 [ib_core]
    [&amp;lt;ffffffffc263949e&amp;gt;] ib_register_device+0x9e/0x3a0 [ib_core]
    [&amp;lt;ffffffffc2a3d389&amp;gt;] 0xffffffffc2a3d389
    [&amp;lt;ffffffffc2688cd8&amp;gt;] nldev_newlink+0x2b8/0x520 [ib_core]
    [&amp;lt;ffffffffc2645fe3&amp;gt;] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]
    [&amp;lt;ffffffffc26464…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-38539</guid>
    </item>
    <item>
      <title>GHSA-vmv4-cp43-whx4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vmv4-cp43-whx4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw&lt;/p&gt;
&lt;p&gt;When running blktests nvme/rdma, the following kmemleak issue will appear.&lt;/p&gt;
&lt;p&gt;kmemleak: Kernel memory leak detector initialized (mempool available:36041)
kmemleak: Automatic memory scanning thread started
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88855da53400 (size 192):
  comm &amp;#34;rdma&amp;#34;, pid 10630, jiffies 4296575922
  hex dump (first 32 bytes):
    37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00  7...............
    10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff  .4.].....4.]....
  backtrace (crc 47f66721):
    [&amp;lt;ffffffff911251bd&amp;gt;] kmalloc_trace+0x30d/0x3b0
    [&amp;lt;ffffffffc2640ff7&amp;gt;] alloc_gid_entry+0x47/0x380 [ib_core]
    [&amp;lt;ffffffffc2642206&amp;gt;] add_modify_gid+0x166/0x930 [ib_core]
    [&amp;lt;ffffffffc2643468&amp;gt;] ib_cache_update.part.0+0x6d8/0x910 [ib_core]
    [&amp;lt;ffffffffc2644e1a&amp;gt;] ib_cache_setup_one+0x24a/0x350 [ib_core]
    [&amp;lt;ffffffffc263949e&amp;gt;] ib_register_device+0x9e/0x3a0 [ib_core]
    [&amp;lt;ffffffffc2a3d389&amp;gt;] 0xffffffffc2a3d389
    [&amp;lt;ffffffffc2688cd8&amp;gt;] nldev_newlink+0x2b8/0x520 [ib_core]
    [&amp;lt;ffffffffc2645fe3&amp;gt;] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]
    [&amp;lt;ffffffffc26464…&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;RDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw&lt;/p&gt;
&lt;p&gt;When running blktests nvme/rdma, the following kmemleak issue will appear.&lt;/p&gt;
&lt;p&gt;kmemleak: Kernel memory leak detector initialized (mempool available:36041)
kmemleak: Automatic memory scanning thread started
kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak)
kmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak)&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff88855da53400 (size 192):
  comm &amp;#34;rdma&amp;#34;, pid 10630, jiffies 4296575922
  hex dump (first 32 bytes):
    37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00  7...............
    10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff  .4.].....4.]....
  backtrace (crc 47f66721):
    [&amp;lt;ffffffff911251bd&amp;gt;] kmalloc_trace+0x30d/0x3b0
    [&amp;lt;ffffffffc2640ff7&amp;gt;] alloc_gid_entry+0x47/0x380 [ib_core]
    [&amp;lt;ffffffffc2642206&amp;gt;] add_modify_gid+0x166/0x930 [ib_core]
    [&amp;lt;ffffffffc2643468&amp;gt;] ib_cache_update.part.0+0x6d8/0x910 [ib_core]
    [&amp;lt;ffffffffc2644e1a&amp;gt;] ib_cache_setup_one+0x24a/0x350 [ib_core]
    [&amp;lt;ffffffffc263949e&amp;gt;] ib_register_device+0x9e/0x3a0 [ib_core]
    [&amp;lt;ffffffffc2a3d389&amp;gt;] 0xffffffffc2a3d389
    [&amp;lt;ffffffffc2688cd8&amp;gt;] nldev_newlink+0x2b8/0x520 [ib_core]
    [&amp;lt;ffffffffc2645fe3&amp;gt;] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]
    [&amp;lt;ffffffffc26464…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vmv4-cp43-whx4</guid>
    </item>
    <item>
      <title>OESA-2024-2076 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2076</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ipvlan: Dont Use skb-&amp;amp;gt;sk in ipvlan_process_v{4,6}_outbound&#13;
&#13;
Raw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will
hit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.&#13;
&#13;
WARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70
Modules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper
CPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
RIP: 0010:sk_mc_loop+0x2d/0x70
Code: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c
RSP: 0018:ffffa9584015cd78 EFLAGS: 00010212
RAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001
RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000
RBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00
R10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000
R13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000
FS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
&amp;amp;lt;IRQ&amp;amp;gt;
 ?…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ipvlan: Dont Use skb-&amp;amp;gt;sk in ipvlan_process_v{4,6}_outbound&#13;
&#13;
Raw packet from PF_PACKET socket ontop of an IPv6-backed ipvlan device will
hit WARN_ON_ONCE() in sk_mc_loop() through sch_direct_xmit() path.&#13;
&#13;
WARNING: CPU: 2 PID: 0 at net/core/sock.c:775 sk_mc_loop+0x2d/0x70
Modules linked in: sch_netem ipvlan rfkill cirrus drm_shmem_helper sg drm_kms_helper
CPU: 2 PID: 0 Comm: swapper/2 Kdump: loaded Not tainted 6.9.0+ #279
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014
RIP: 0010:sk_mc_loop+0x2d/0x70
Code: fa 0f 1f 44 00 00 65 0f b7 15 f7 96 a3 4f 31 c0 66 85 d2 75 26 48 85 ff 74 1c
RSP: 0018:ffffa9584015cd78 EFLAGS: 00010212
RAX: 0000000000000011 RBX: ffff91e585793e00 RCX: 0000000002c6a001
RDX: 0000000000000000 RSI: 0000000000000040 RDI: ffff91e589c0f000
RBP: ffff91e5855bd100 R08: 0000000000000000 R09: 3d00545216f43d00
R10: ffff91e584fdcc50 R11: 00000060dd8616f4 R12: ffff91e58132d000
R13: ffff91e584fdcc68 R14: ffff91e5869ce800 R15: ffff91e589c0f000
FS:  0000000000000000(0000) GS:ffff91e898100000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f788f7c44c0 CR3: 0000000008e1a000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
&amp;amp;lt;IRQ&amp;amp;gt;
 ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2076</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2571-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2571-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-2024:2571-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-38539</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-38539</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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw When running blktests nvme/rdma, the following kmemleak issue will appear. kmemleak: Kernel memory leak detector initialized (mempool available:36041) kmemleak: Automatic memory scanning thread started kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak) unreferenced object 0xffff88855da53400 (size 192):   comm &amp;#34;rdma&amp;#34;, pid 10630, jiffies 4296575922   hex dump (first 32 bytes):     37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00  7...............     10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff  .4.].....4.]....   backtrace (crc 47f66721):     [&amp;lt;ffffffff911251bd&amp;gt;] kmalloc_trace+0x30d/0x3b0     [&amp;lt;ffffffffc2640ff7&amp;gt;] alloc_gid_entry+0x47/0x380 [ib_core]     [&amp;lt;ffffffffc2642206&amp;gt;] add_modify_gid+0x166/0x930 [ib_core]     [&amp;lt;ffffffffc2643468&amp;gt;] ib_cache_update.part.0+0x6d8/0x910 [ib_core]     [&amp;lt;ffffffffc2644e1a&amp;gt;] ib_cache_setup_one+0x24a/0x350 [ib_core]     [&amp;lt;ffffffffc263949e&amp;gt;] ib_register_device+0x9e/0x3a0 [ib_core]     [&amp;lt;ffffffffc2a3d389&amp;gt;] 0xffffffffc2a3d389     [&amp;lt;ffffffffc2688cd8&amp;gt;] nldev_newlink+0x2b8/0x520 [ib_core]     [&amp;lt;ffffffffc2645fe3&amp;gt;] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]     [&amp;lt;ffffffffc264648c&amp;gt;]…&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 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/cma: Fix kmemleak in rdma_core observed during blktests nvme/rdma use siw When running blktests nvme/rdma, the following kmemleak issue will appear. kmemleak: Kernel memory leak detector initialized (mempool available:36041) kmemleak: Automatic memory scanning thread started kmemleak: 2 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 8 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 17 new suspected memory leaks (see /sys/kernel/debug/kmemleak) kmemleak: 4 new suspected memory leaks (see /sys/kernel/debug/kmemleak) unreferenced object 0xffff88855da53400 (size 192):   comm &amp;#34;rdma&amp;#34;, pid 10630, jiffies 4296575922   hex dump (first 32 bytes):     37 00 00 00 00 00 00 00 c0 ff ff ff 1f 00 00 00  7...............     10 34 a5 5d 85 88 ff ff 10 34 a5 5d 85 88 ff ff  .4.].....4.]....   backtrace (crc 47f66721):     [&amp;lt;ffffffff911251bd&amp;gt;] kmalloc_trace+0x30d/0x3b0     [&amp;lt;ffffffffc2640ff7&amp;gt;] alloc_gid_entry+0x47/0x380 [ib_core]     [&amp;lt;ffffffffc2642206&amp;gt;] add_modify_gid+0x166/0x930 [ib_core]     [&amp;lt;ffffffffc2643468&amp;gt;] ib_cache_update.part.0+0x6d8/0x910 [ib_core]     [&amp;lt;ffffffffc2644e1a&amp;gt;] ib_cache_setup_one+0x24a/0x350 [ib_core]     [&amp;lt;ffffffffc263949e&amp;gt;] ib_register_device+0x9e/0x3a0 [ib_core]     [&amp;lt;ffffffffc2a3d389&amp;gt;] 0xffffffffc2a3d389     [&amp;lt;ffffffffc2688cd8&amp;gt;] nldev_newlink+0x2b8/0x520 [ib_core]     [&amp;lt;ffffffffc2645fe3&amp;gt;] rdma_nl_rcv_msg+0x2c3/0x520 [ib_core]     [&amp;lt;ffffffffc264648c&amp;gt;]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-38539</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1418 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1418</guid>
    </item>
  </channel>
</rss>
