<?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 08:51:27 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03701</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03701</link>
      <description>bdu:2024-03701</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03701</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26833</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26833</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-2024-26833</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0381 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0381</link>
      <description>certfr-2024-avi-0381</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0381</guid>
    </item>
    <item>
      <title>EUVD-2026-312619</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312619</link>
      <description>EUVD-2026-312619</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312619</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26833</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26833</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Fix memory leak in dm_sw_fini()&lt;/p&gt;
&lt;p&gt;After destroying dmub_srv, the memory associated with it is
not freed, causing a memory leak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff896302b45800 (size 1024):
  comm &amp;#34;(udev-worker)&amp;#34;, pid 222, jiffies 4294894636
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 6265fd77):
    [&amp;lt;ffffffff993495ed&amp;gt;] kmalloc_trace+0x29d/0x340
    [&amp;lt;ffffffffc0ea4a94&amp;gt;] dm_dmub_sw_init+0xb4/0x450 [amdgpu]
    [&amp;lt;ffffffffc0ea4e55&amp;gt;] dm_sw_init+0x15/0x2b0 [amdgpu]
    [&amp;lt;ffffffffc0ba8557&amp;gt;] amdgpu_device_init+0x1417/0x24e0 [amdgpu]
    [&amp;lt;ffffffffc0bab285&amp;gt;] amdgpu_driver_load_kms+0x15/0x190 [amdgpu]
    [&amp;lt;ffffffffc0ba09c7&amp;gt;] amdgpu_pci_probe+0x187/0x4e0 [amdgpu]
    [&amp;lt;ffffffff9968fd1e&amp;gt;] local_pci_probe+0x3e/0x90
    [&amp;lt;ffffffff996918a3&amp;gt;] pci_device_probe+0xc3/0x230
    [&amp;lt;ffffffff99805872&amp;gt;] really_probe+0xe2/0x480
    [&amp;lt;ffffffff99805c98&amp;gt;] __driver_probe_device+0x78/0x160
    [&amp;lt;ffffffff99805daf&amp;gt;] driver_probe_device+0x1f/0x90
    [&amp;lt;ffffffff9980601e&amp;gt;] __driver_attach+0xce/0x1c0
    [&amp;lt;ffffffff99803170&amp;gt;] bus_for_each_dev+0x70/0xc0
    [&amp;lt;ffffffff99804822&amp;gt;] bus_add_driver+0x112/0x210
    [&amp;lt;ffffffff99807245&amp;gt;] driver_register+0x55/0x100
    [&amp;lt;ffffffff990012d1&amp;gt;] do_one_initcall+0x41/0x300&lt;/p&gt;
&lt;p&gt;Fix this by freeing dmub_srv after destroying it.&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;drm/amd/display: Fix memory leak in dm_sw_fini()&lt;/p&gt;
&lt;p&gt;After destroying dmub_srv, the memory associated with it is
not freed, causing a memory leak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff896302b45800 (size 1024):
  comm &amp;#34;(udev-worker)&amp;#34;, pid 222, jiffies 4294894636
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 6265fd77):
    [&amp;lt;ffffffff993495ed&amp;gt;] kmalloc_trace+0x29d/0x340
    [&amp;lt;ffffffffc0ea4a94&amp;gt;] dm_dmub_sw_init+0xb4/0x450 [amdgpu]
    [&amp;lt;ffffffffc0ea4e55&amp;gt;] dm_sw_init+0x15/0x2b0 [amdgpu]
    [&amp;lt;ffffffffc0ba8557&amp;gt;] amdgpu_device_init+0x1417/0x24e0 [amdgpu]
    [&amp;lt;ffffffffc0bab285&amp;gt;] amdgpu_driver_load_kms+0x15/0x190 [amdgpu]
    [&amp;lt;ffffffffc0ba09c7&amp;gt;] amdgpu_pci_probe+0x187/0x4e0 [amdgpu]
    [&amp;lt;ffffffff9968fd1e&amp;gt;] local_pci_probe+0x3e/0x90
    [&amp;lt;ffffffff996918a3&amp;gt;] pci_device_probe+0xc3/0x230
    [&amp;lt;ffffffff99805872&amp;gt;] really_probe+0xe2/0x480
    [&amp;lt;ffffffff99805c98&amp;gt;] __driver_probe_device+0x78/0x160
    [&amp;lt;ffffffff99805daf&amp;gt;] driver_probe_device+0x1f/0x90
    [&amp;lt;ffffffff9980601e&amp;gt;] __driver_attach+0xce/0x1c0
    [&amp;lt;ffffffff99803170&amp;gt;] bus_for_each_dev+0x70/0xc0
    [&amp;lt;ffffffff99804822&amp;gt;] bus_add_driver+0x112/0x210
    [&amp;lt;ffffffff99807245&amp;gt;] driver_register+0x55/0x100
    [&amp;lt;ffffffff990012d1&amp;gt;] do_one_initcall+0x41/0x300&lt;/p&gt;
&lt;p&gt;Fix this by freeing dmub_srv after destroying it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26833</guid>
    </item>
    <item>
      <title>GHSA-jv96-qfmj-26f9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jv96-qfmj-26f9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/amd/display: Fix memory leak in dm_sw_fini()&lt;/p&gt;
&lt;p&gt;After destroying dmub_srv, the memory associated with it is
not freed, causing a memory leak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff896302b45800 (size 1024):
  comm &amp;#34;(udev-worker)&amp;#34;, pid 222, jiffies 4294894636
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 6265fd77):
    [&amp;lt;ffffffff993495ed&amp;gt;] kmalloc_trace+0x29d/0x340
    [&amp;lt;ffffffffc0ea4a94&amp;gt;] dm_dmub_sw_init+0xb4/0x450 [amdgpu]
    [&amp;lt;ffffffffc0ea4e55&amp;gt;] dm_sw_init+0x15/0x2b0 [amdgpu]
    [&amp;lt;ffffffffc0ba8557&amp;gt;] amdgpu_device_init+0x1417/0x24e0 [amdgpu]
    [&amp;lt;ffffffffc0bab285&amp;gt;] amdgpu_driver_load_kms+0x15/0x190 [amdgpu]
    [&amp;lt;ffffffffc0ba09c7&amp;gt;] amdgpu_pci_probe+0x187/0x4e0 [amdgpu]
    [&amp;lt;ffffffff9968fd1e&amp;gt;] local_pci_probe+0x3e/0x90
    [&amp;lt;ffffffff996918a3&amp;gt;] pci_device_probe+0xc3/0x230
    [&amp;lt;ffffffff99805872&amp;gt;] really_probe+0xe2/0x480
    [&amp;lt;ffffffff99805c98&amp;gt;] __driver_probe_device+0x78/0x160
    [&amp;lt;ffffffff99805daf&amp;gt;] driver_probe_device+0x1f/0x90
    [&amp;lt;ffffffff9980601e&amp;gt;] __driver_attach+0xce/0x1c0
    [&amp;lt;ffffffff99803170&amp;gt;] bus_for_each_dev+0x70/0xc0
    [&amp;lt;ffffffff99804822&amp;gt;] bus_add_driver+0x112/0x210
    [&amp;lt;ffffffff99807245&amp;gt;] driver_register+0x55/0x100
    [&amp;lt;ffffffff990012d1&amp;gt;] do_one_initcall+0x41/0x300&lt;/p&gt;
&lt;p&gt;Fix this by freeing dmub_srv after destroying it.&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;drm/amd/display: Fix memory leak in dm_sw_fini()&lt;/p&gt;
&lt;p&gt;After destroying dmub_srv, the memory associated with it is
not freed, causing a memory leak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff896302b45800 (size 1024):
  comm &amp;#34;(udev-worker)&amp;#34;, pid 222, jiffies 4294894636
  hex dump (first 32 bytes):
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
  backtrace (crc 6265fd77):
    [&amp;lt;ffffffff993495ed&amp;gt;] kmalloc_trace+0x29d/0x340
    [&amp;lt;ffffffffc0ea4a94&amp;gt;] dm_dmub_sw_init+0xb4/0x450 [amdgpu]
    [&amp;lt;ffffffffc0ea4e55&amp;gt;] dm_sw_init+0x15/0x2b0 [amdgpu]
    [&amp;lt;ffffffffc0ba8557&amp;gt;] amdgpu_device_init+0x1417/0x24e0 [amdgpu]
    [&amp;lt;ffffffffc0bab285&amp;gt;] amdgpu_driver_load_kms+0x15/0x190 [amdgpu]
    [&amp;lt;ffffffffc0ba09c7&amp;gt;] amdgpu_pci_probe+0x187/0x4e0 [amdgpu]
    [&amp;lt;ffffffff9968fd1e&amp;gt;] local_pci_probe+0x3e/0x90
    [&amp;lt;ffffffff996918a3&amp;gt;] pci_device_probe+0xc3/0x230
    [&amp;lt;ffffffff99805872&amp;gt;] really_probe+0xe2/0x480
    [&amp;lt;ffffffff99805c98&amp;gt;] __driver_probe_device+0x78/0x160
    [&amp;lt;ffffffff99805daf&amp;gt;] driver_probe_device+0x1f/0x90
    [&amp;lt;ffffffff9980601e&amp;gt;] __driver_attach+0xce/0x1c0
    [&amp;lt;ffffffff99803170&amp;gt;] bus_for_each_dev+0x70/0xc0
    [&amp;lt;ffffffff99804822&amp;gt;] bus_add_driver+0x112/0x210
    [&amp;lt;ffffffff99807245&amp;gt;] driver_register+0x55/0x100
    [&amp;lt;ffffffff990012d1&amp;gt;] do_one_initcall+0x41/0x300&lt;/p&gt;
&lt;p&gt;Fix this by freeing dmub_srv after destroying it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jv96-qfmj-26f9</guid>
    </item>
    <item>
      <title>gsd-2024-26833</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26833</link>
      <description>gsd-2024-26833</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26833</guid>
    </item>
    <item>
      <title>OESA-2024-1693 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1693</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
mptcp: ensure tx skbs always have the MPTCP ext&#13;
&#13;
Due to signed/unsigned comparison, the expression:&#13;
&#13;
	info-&amp;amp;gt;size_goal - skb-&amp;amp;gt;len &amp;amp;gt; 0&#13;
&#13;
evaluates to true when the size goal is smaller than the
skb size. That results in lack of tx cache refill, so that
the skb allocated by the core TCP code lacks the required
MPTCP skb extensions.&#13;
&#13;
Due to the above, syzbot is able to trigger the following WARN_ON():&#13;
&#13;
WARNING: CPU: 1 PID: 810 at net/mptcp/protocol.c:1366 mptcp_sendmsg_frag+0x1362/0x1bc0 net/mptcp/protocol.c:1366
Modules linked in:
CPU: 1 PID: 810 Comm: syz-executor.4 Not tainted 5.14.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:mptcp_sendmsg_frag+0x1362/0x1bc0 net/mptcp/protocol.c:1366
Code: ff 4c 8b 74 24 50 48 8b 5c 24 58 e9 0f fb ff ff e8 13 44 8b f8 4c 89 e7 45 31 ed e8 98 57 2e fe e9 81 f4 ff ff e8 fe 43 8b f8 &amp;amp;lt;0f&amp;amp;gt; 0b 41 bd ea ff ff ff e9 6f f4 ff ff 4c 89 e7 e8 b9 8e d2 f8 e9
RSP: 0018:ffffc9000531f6a0 EFLAGS: 00010216
RAX: 000000000000697f RBX: 0000000000000000 RCX: ffffc90012107000
RDX: 0000000000040000 RSI: ffffffff88eac9e2 RDI: 0000000000000003
RBP: ffff888078b15780 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff88eac017 R11: 0000000000000000 R12: ffff88801de0a280
R13: 0000000000006b58 R14: ffff888066278280 R15: ffff88803…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP1: 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;
mptcp: ensure tx skbs always have the MPTCP ext&#13;
&#13;
Due to signed/unsigned comparison, the expression:&#13;
&#13;
	info-&amp;amp;gt;size_goal - skb-&amp;amp;gt;len &amp;amp;gt; 0&#13;
&#13;
evaluates to true when the size goal is smaller than the
skb size. That results in lack of tx cache refill, so that
the skb allocated by the core TCP code lacks the required
MPTCP skb extensions.&#13;
&#13;
Due to the above, syzbot is able to trigger the following WARN_ON():&#13;
&#13;
WARNING: CPU: 1 PID: 810 at net/mptcp/protocol.c:1366 mptcp_sendmsg_frag+0x1362/0x1bc0 net/mptcp/protocol.c:1366
Modules linked in:
CPU: 1 PID: 810 Comm: syz-executor.4 Not tainted 5.14.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:mptcp_sendmsg_frag+0x1362/0x1bc0 net/mptcp/protocol.c:1366
Code: ff 4c 8b 74 24 50 48 8b 5c 24 58 e9 0f fb ff ff e8 13 44 8b f8 4c 89 e7 45 31 ed e8 98 57 2e fe e9 81 f4 ff ff e8 fe 43 8b f8 &amp;amp;lt;0f&amp;amp;gt; 0b 41 bd ea ff ff ff e9 6f f4 ff ff 4c 89 e7 e8 b9 8e d2 f8 e9
RSP: 0018:ffffc9000531f6a0 EFLAGS: 00010216
RAX: 000000000000697f RBX: 0000000000000000 RCX: ffffc90012107000
RDX: 0000000000040000 RSI: ffffffff88eac9e2 RDI: 0000000000000003
RBP: ffff888078b15780 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff88eac017 R11: 0000000000000000 R12: ffff88801de0a280
R13: 0000000000006b58 R14: ffff888066278280 R15: ffff88803…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1693</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1644-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1644-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:1644-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26833</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26833</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak in dm_sw_fini() After destroying dmub_srv, the memory associated with it is not freed, causing a memory leak: unreferenced object 0xffff896302b45800 (size 1024):   comm &amp;#34;(udev-worker)&amp;#34;, pid 222, jiffies 4294894636   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace (crc 6265fd77):     [&amp;lt;ffffffff993495ed&amp;gt;] kmalloc_trace+0x29d/0x340     [&amp;lt;ffffffffc0ea4a94&amp;gt;] dm_dmub_sw_init+0xb4/0x450 [amdgpu]     [&amp;lt;ffffffffc0ea4e55&amp;gt;] dm_sw_init+0x15/0x2b0 [amdgpu]     [&amp;lt;ffffffffc0ba8557&amp;gt;] amdgpu_device_init+0x1417/0x24e0 [amdgpu]     [&amp;lt;ffffffffc0bab285&amp;gt;] amdgpu_driver_load_kms+0x15/0x190 [amdgpu]     [&amp;lt;ffffffffc0ba09c7&amp;gt;] amdgpu_pci_probe+0x187/0x4e0 [amdgpu]     [&amp;lt;ffffffff9968fd1e&amp;gt;] local_pci_probe+0x3e/0x90     [&amp;lt;ffffffff996918a3&amp;gt;] pci_device_probe+0xc3/0x230     [&amp;lt;ffffffff99805872&amp;gt;] really_probe+0xe2/0x480     [&amp;lt;ffffffff99805c98&amp;gt;] __driver_probe_device+0x78/0x160     [&amp;lt;ffffffff99805daf&amp;gt;] driver_probe_device+0x1f/0x90     [&amp;lt;ffffffff9980601e&amp;gt;] __driver_attach+0xce/0x1c0     [&amp;lt;ffffffff99803170&amp;gt;] bus_for_each_dev+0x70/0xc0     [&amp;lt;ffffffff99804822&amp;gt;] bus_add_driver+0x112/0x210     [&amp;lt;ffffffff99807245&amp;gt;] driver_register+0x55/0x100     [&amp;lt;ffffffff990012d1&amp;gt;] do_one_initcall+0x41/0x300 Fix this by freeing dmub_srv after destroying it.&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak in dm_sw_fini() After destroying dmub_srv, the memory associated with it is not freed, causing a memory leak: unreferenced object 0xffff896302b45800 (size 1024):   comm &amp;#34;(udev-worker)&amp;#34;, pid 222, jiffies 4294894636   hex dump (first 32 bytes):     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................   backtrace (crc 6265fd77):     [&amp;lt;ffffffff993495ed&amp;gt;] kmalloc_trace+0x29d/0x340     [&amp;lt;ffffffffc0ea4a94&amp;gt;] dm_dmub_sw_init+0xb4/0x450 [amdgpu]     [&amp;lt;ffffffffc0ea4e55&amp;gt;] dm_sw_init+0x15/0x2b0 [amdgpu]     [&amp;lt;ffffffffc0ba8557&amp;gt;] amdgpu_device_init+0x1417/0x24e0 [amdgpu]     [&amp;lt;ffffffffc0bab285&amp;gt;] amdgpu_driver_load_kms+0x15/0x190 [amdgpu]     [&amp;lt;ffffffffc0ba09c7&amp;gt;] amdgpu_pci_probe+0x187/0x4e0 [amdgpu]     [&amp;lt;ffffffff9968fd1e&amp;gt;] local_pci_probe+0x3e/0x90     [&amp;lt;ffffffff996918a3&amp;gt;] pci_device_probe+0xc3/0x230     [&amp;lt;ffffffff99805872&amp;gt;] really_probe+0xe2/0x480     [&amp;lt;ffffffff99805c98&amp;gt;] __driver_probe_device+0x78/0x160     [&amp;lt;ffffffff99805daf&amp;gt;] driver_probe_device+0x1f/0x90     [&amp;lt;ffffffff9980601e&amp;gt;] __driver_attach+0xce/0x1c0     [&amp;lt;ffffffff99803170&amp;gt;] bus_for_each_dev+0x70/0xc0     [&amp;lt;ffffffff99804822&amp;gt;] bus_add_driver+0x112/0x210     [&amp;lt;ffffffff99807245&amp;gt;] driver_register+0x55/0x100     [&amp;lt;ffffffff990012d1&amp;gt;] do_one_initcall+0x41/0x300 Fix this by freeing dmub_srv after destroying it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26833</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0920 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0920</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht 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 Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0920</guid>
    </item>
  </channel>
</rss>
