<?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 17:54:39 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04317</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04317</link>
      <description>bdu:2025-04317</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04317</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53184</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53184</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-53184</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>EUVD-2026-313647</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313647</link>
      <description>EUVD-2026-313647</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313647</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53184</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53184</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: ubd: Do not use drvdata in release&lt;/p&gt;
&lt;p&gt;The drvdata is not available in release. Let&amp;#39;s just use container_of()
to get the ubd instance. Otherwise, removing a ubd device will result
in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:blk_mq_free_tag_set+0x1f/0xba
RSP: 00000000e2083bf0  EFLAGS: 00010246
RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00
RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348
RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7
R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000
R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0
Kernel panic - not syncing: Segfault with no mm
CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1
Workqueue: events mc_work_proc
Stack:
 00000000 604f7ef0 62c5d000 62405d20
 e2083c30 6002c776 6002c755 600e47ff
 e2083c60 6025ffe3 04208060 603d36e0
Call Trace:
 [&amp;lt;6002c776&amp;gt;] ubd_device_release+0x21/0x55
 [&amp;lt;6002c755&amp;gt;] ? ubd_device_release+0x0/0x55
 [&amp;lt;600e47ff&amp;gt;] ? kfree+0x0/0x100
 [&amp;lt;6025ffe3&amp;gt;] device_release+0x70/0xba
 [&amp;lt;60381d6a&amp;gt;] kobject_put+0xb5/0xe2
 [&amp;lt;6026027b&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;6026a036&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;6026ac5a&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;6002c52e&amp;gt;] ubd_remove+0xb8/0xd6
 [&amp;lt;6002bb74&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;6002b926&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;6002bbbc&amp;gt;] ? mconsole_reply+0x48/0x50
 [&amp;lt;6003379c&amp;gt;] ? um_set_signals+0x3b/0x43
 [&amp;lt;60061c55&amp;gt;] ?…&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;um: ubd: Do not use drvdata in release&lt;/p&gt;
&lt;p&gt;The drvdata is not available in release. Let&amp;#39;s just use container_of()
to get the ubd instance. Otherwise, removing a ubd device will result
in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:blk_mq_free_tag_set+0x1f/0xba
RSP: 00000000e2083bf0  EFLAGS: 00010246
RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00
RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348
RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7
R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000
R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0
Kernel panic - not syncing: Segfault with no mm
CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1
Workqueue: events mc_work_proc
Stack:
 00000000 604f7ef0 62c5d000 62405d20
 e2083c30 6002c776 6002c755 600e47ff
 e2083c60 6025ffe3 04208060 603d36e0
Call Trace:
 [&amp;lt;6002c776&amp;gt;] ubd_device_release+0x21/0x55
 [&amp;lt;6002c755&amp;gt;] ? ubd_device_release+0x0/0x55
 [&amp;lt;600e47ff&amp;gt;] ? kfree+0x0/0x100
 [&amp;lt;6025ffe3&amp;gt;] device_release+0x70/0xba
 [&amp;lt;60381d6a&amp;gt;] kobject_put+0xb5/0xe2
 [&amp;lt;6026027b&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;6026a036&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;6026ac5a&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;6002c52e&amp;gt;] ubd_remove+0xb8/0xd6
 [&amp;lt;6002bb74&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;6002b926&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;6002bbbc&amp;gt;] ? mconsole_reply+0x48/0x50
 [&amp;lt;6003379c&amp;gt;] ? um_set_signals+0x3b/0x43
 [&amp;lt;60061c55&amp;gt;] ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53184</guid>
    </item>
    <item>
      <title>GHSA-6phj-4x32-mh52</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6phj-4x32-mh52</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: ubd: Do not use drvdata in release&lt;/p&gt;
&lt;p&gt;The drvdata is not available in release. Let&amp;#39;s just use container_of()
to get the ubd instance. Otherwise, removing a ubd device will result
in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:blk_mq_free_tag_set+0x1f/0xba
RSP: 00000000e2083bf0  EFLAGS: 00010246
RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00
RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348
RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7
R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000
R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0
Kernel panic - not syncing: Segfault with no mm
CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1
Workqueue: events mc_work_proc
Stack:
 00000000 604f7ef0 62c5d000 62405d20
 e2083c30 6002c776 6002c755 600e47ff
 e2083c60 6025ffe3 04208060 603d36e0
Call Trace:
 [&amp;lt;6002c776&amp;gt;] ubd_device_release+0x21/0x55
 [&amp;lt;6002c755&amp;gt;] ? ubd_device_release+0x0/0x55
 [&amp;lt;600e47ff&amp;gt;] ? kfree+0x0/0x100
 [&amp;lt;6025ffe3&amp;gt;] device_release+0x70/0xba
 [&amp;lt;60381d6a&amp;gt;] kobject_put+0xb5/0xe2
 [&amp;lt;6026027b&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;6026a036&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;6026ac5a&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;6002c52e&amp;gt;] ubd_remove+0xb8/0xd6
 [&amp;lt;6002bb74&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;6002b926&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;6002bbbc&amp;gt;] ? mconsole_reply+0x48/0x50
 [&amp;lt;6003379c&amp;gt;] ? um_set_signals+0x3b/0x43
 [&amp;lt;60061c55&amp;gt;] ?…&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;um: ubd: Do not use drvdata in release&lt;/p&gt;
&lt;p&gt;The drvdata is not available in release. Let&amp;#39;s just use container_of()
to get the ubd instance. Otherwise, removing a ubd device will result
in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:blk_mq_free_tag_set+0x1f/0xba
RSP: 00000000e2083bf0  EFLAGS: 00010246
RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00
RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348
RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7
R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000
R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0
Kernel panic - not syncing: Segfault with no mm
CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1
Workqueue: events mc_work_proc
Stack:
 00000000 604f7ef0 62c5d000 62405d20
 e2083c30 6002c776 6002c755 600e47ff
 e2083c60 6025ffe3 04208060 603d36e0
Call Trace:
 [&amp;lt;6002c776&amp;gt;] ubd_device_release+0x21/0x55
 [&amp;lt;6002c755&amp;gt;] ? ubd_device_release+0x0/0x55
 [&amp;lt;600e47ff&amp;gt;] ? kfree+0x0/0x100
 [&amp;lt;6025ffe3&amp;gt;] device_release+0x70/0xba
 [&amp;lt;60381d6a&amp;gt;] kobject_put+0xb5/0xe2
 [&amp;lt;6026027b&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;6026a036&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;6026ac5a&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;6002c52e&amp;gt;] ubd_remove+0xb8/0xd6
 [&amp;lt;6002bb74&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;6002b926&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;6002bbbc&amp;gt;] ? mconsole_reply+0x48/0x50
 [&amp;lt;6003379c&amp;gt;] ? um_set_signals+0x3b/0x43
 [&amp;lt;60061c55&amp;gt;] ?…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6phj-4x32-mh52</guid>
    </item>
    <item>
      <title>ICSA-25-226-07 — Siemens Third-Party Components in SINEC OS</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-25-226-07</link>
      <description>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-25-226-07</guid>
    </item>
    <item>
      <title>OESA-2025-1034 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1034</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK  When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning similar as below when showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs.  [    3.052463] ------------[ cut here ]------------ [    3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [    3.070072] Modules linked in: efivarfs autofs4 [    3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [    3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [    3.109127]         9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [    3.118774]         90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [    3.128412]         0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [    3.138056]         0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [    3.147711]         ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [    3.157364]         900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [    3.167012]         0000000000000009 000000000000006c 0000000000000000 0000000000000000 [    3.176641]         9000000000d3de08 9000000001…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:  sh: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK  When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning similar as below when showing /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit) instead of NR_CPUS to iterate CPUs.  [    3.052463] ------------[ cut here ]------------ [    3.059679] WARNING: CPU: 3 PID: 1 at include/linux/cpumask.h:108 show_cpuinfo+0x5e8/0x5f0 [    3.070072] Modules linked in: efivarfs autofs4 [    3.076257] CPU: 0 PID: 1 Comm: systemd Not tainted 5.19-rc5+ #1052 [    3.099465] Stack : 9000000100157b08 9000000000f18530 9000000000cf846c 9000000100154000 [    3.109127]         9000000100157a50 0000000000000000 9000000100157a58 9000000000ef7430 [    3.118774]         90000001001578e8 0000000000000040 0000000000000020 ffffffffffffffff [    3.128412]         0000000000aaaaaa 1ab25f00eec96a37 900000010021de80 900000000101c890 [    3.138056]         0000000000000000 0000000000000000 0000000000000000 0000000000aaaaaa [    3.147711]         ffff8000339dc220 0000000000000001 0000000006ab4000 0000000000000000 [    3.157364]         900000000101c998 0000000000000004 9000000000ef7430 0000000000000000 [    3.167012]         0000000000000009 000000000000006c 0000000000000000 0000000000000000 [    3.176641]         9000000000d3de08 9000000001…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1034</guid>
    </item>
    <item>
      <title>SSA-355557 — SSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-355557</link>
      <description>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-355557</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-53184</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53184</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: um: ubd: Do not use drvdata in release The drvdata is not available in release. Let&amp;#39;s just use container_of() to get the ubd instance. Otherwise, removing a ubd device will result in a crash: RIP: 0033:blk_mq_free_tag_set+0x1f/0xba RSP: 00000000e2083bf0  EFLAGS: 00010246 RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00 RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348 RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7 R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000 R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0 Kernel panic - not syncing: Segfault with no mm CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1 Workqueue: events mc_work_proc Stack:  00000000 604f7ef0 62c5d000 62405d20  e2083c30 6002c776 6002c755 600e47ff  e2083c60 6025ffe3 04208060 603d36e0 Call Trace:  [&amp;lt;6002c776&amp;gt;] ubd_device_release+0x21/0x55  [&amp;lt;6002c755&amp;gt;] ? ubd_device_release+0x0/0x55  [&amp;lt;600e47ff&amp;gt;] ? kfree+0x0/0x100  [&amp;lt;6025ffe3&amp;gt;] device_release+0x70/0xba  [&amp;lt;60381d6a&amp;gt;] kobject_put+0xb5/0xe2  [&amp;lt;6026027b&amp;gt;] put_device+0x19/0x1c  [&amp;lt;6026a036&amp;gt;] platform_device_put+0x26/0x29  [&amp;lt;6026ac5a&amp;gt;] platform_device_unregister+0x2c/0x2e  [&amp;lt;6002c52e&amp;gt;] ubd_remove+0xb8/0xd6  [&amp;lt;6002bb74&amp;gt;] ? mconsole_reply+0x0/0x50  [&amp;lt;6002b926&amp;gt;] mconsole_remove+0x160/0x1cc  [&amp;lt;6002bbbc&amp;gt;] ? mconsole_reply+0x48/0x50  [&amp;lt;6003379c&amp;gt;] ? um_set_signals+0x3b/0x43  [&amp;lt;60061c55&amp;gt;] ? upd…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: um: ubd: Do not use drvdata in release The drvdata is not available in release. Let&amp;#39;s just use container_of() to get the ubd instance. Otherwise, removing a ubd device will result in a crash: RIP: 0033:blk_mq_free_tag_set+0x1f/0xba RSP: 00000000e2083bf0  EFLAGS: 00010246 RAX: 000000006021463a RBX: 0000000000000348 RCX: 0000000062604d00 RDX: 0000000004208060 RSI: 00000000605241a0 RDI: 0000000000000348 RBP: 00000000e2083c10 R08: 0000000062414010 R09: 00000000601603f7 R10: 000000000000133a R11: 000000006038c4bd R12: 0000000000000000 R13: 0000000060213a5c R14: 0000000062405d20 R15: 00000000604f7aa0 Kernel panic - not syncing: Segfault with no mm CPU: 0 PID: 17 Comm: kworker/0:1 Not tainted 6.8.0-rc3-00107-gba3f67c11638 #1 Workqueue: events mc_work_proc Stack:  00000000 604f7ef0 62c5d000 62405d20  e2083c30 6002c776 6002c755 600e47ff  e2083c60 6025ffe3 04208060 603d36e0 Call Trace:  [&amp;lt;6002c776&amp;gt;] ubd_device_release+0x21/0x55  [&amp;lt;6002c755&amp;gt;] ? ubd_device_release+0x0/0x55  [&amp;lt;600e47ff&amp;gt;] ? kfree+0x0/0x100  [&amp;lt;6025ffe3&amp;gt;] device_release+0x70/0xba  [&amp;lt;60381d6a&amp;gt;] kobject_put+0xb5/0xe2  [&amp;lt;6026027b&amp;gt;] put_device+0x19/0x1c  [&amp;lt;6026a036&amp;gt;] platform_device_put+0x26/0x29  [&amp;lt;6026ac5a&amp;gt;] platform_device_unregister+0x2c/0x2e  [&amp;lt;6002c52e&amp;gt;] ubd_remove+0xb8/0xd6  [&amp;lt;6002bb74&amp;gt;] ? mconsole_reply+0x0/0x50  [&amp;lt;6002b926&amp;gt;] mconsole_remove+0x160/0x1cc  [&amp;lt;6002bbbc&amp;gt;] ? mconsole_reply+0x48/0x50  [&amp;lt;6003379c&amp;gt;] ? um_set_signals+0x3b/0x43  [&amp;lt;60061c55&amp;gt;] ? upd…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53184</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
