<?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:06:23 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04319</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04319</link>
      <description>bdu:2025-04319</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04319</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-53181</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-53181</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-53181</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-313645</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313645</link>
      <description>EUVD-2026-313645</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313645</guid>
    </item>
    <item>
      <title>fkie_cve-2024-53181</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-53181</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: vector: 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 vector_device instance. Otherwise, removing a vector device
will result in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:vector_device_release+0xf/0x50
RSP: 00000000e187bc40  EFLAGS: 00010202
RAX: 0000000060028f61 RBX: 00000000600f1baf RCX: 00000000620074e0
RDX: 000000006220b9c0 RSI: 0000000060551c80 RDI: 0000000000000000
RBP: 00000000e187bc50 R08: 00000000603ad594 R09: 00000000e187bb70
R10: 000000000000135a R11: 00000000603ad422 R12: 00000000623ae028
R13: 000000006287a200 R14: 0000000062006d30 R15: 00000000623700b6
Kernel panic - not syncing: Segfault with no mm
CPU: 0 UID: 0 PID: 16 Comm: kworker/0:1 Not tainted 6.12.0-rc6-g59b723cd2adb #1
Workqueue: events mc_work_proc
Stack:
 60028f61 623ae028 e187bc80 60276fcd
 6220b9c0 603f5820 623ae028 00000000
 e187bcb0 603a2bcd 623ae000 62370010
Call Trace:
 [&amp;lt;60028f61&amp;gt;] ? vector_device_release+0x0/0x50
 [&amp;lt;60276fcd&amp;gt;] device_release+0x70/0xba
 [&amp;lt;603a2bcd&amp;gt;] kobject_put+0xba/0xe7
 [&amp;lt;60277265&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;60281266&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;60281e5f&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;60029422&amp;gt;] vector_remove+0x52/0x58
 [&amp;lt;60031316&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;600310c8&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;603b19f4&amp;gt;] ? strlen+0x0/0x15
 [&amp;lt;60066611&amp;gt;] ? __dequeue_entity+0x1a9/0x206
 [&amp;lt;600666a7&amp;gt;] ? set_next_entity+0x39/0x63
 [&amp;lt;6006666e&amp;gt;] ? set_next_enti…&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: vector: 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 vector_device instance. Otherwise, removing a vector device
will result in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:vector_device_release+0xf/0x50
RSP: 00000000e187bc40  EFLAGS: 00010202
RAX: 0000000060028f61 RBX: 00000000600f1baf RCX: 00000000620074e0
RDX: 000000006220b9c0 RSI: 0000000060551c80 RDI: 0000000000000000
RBP: 00000000e187bc50 R08: 00000000603ad594 R09: 00000000e187bb70
R10: 000000000000135a R11: 00000000603ad422 R12: 00000000623ae028
R13: 000000006287a200 R14: 0000000062006d30 R15: 00000000623700b6
Kernel panic - not syncing: Segfault with no mm
CPU: 0 UID: 0 PID: 16 Comm: kworker/0:1 Not tainted 6.12.0-rc6-g59b723cd2adb #1
Workqueue: events mc_work_proc
Stack:
 60028f61 623ae028 e187bc80 60276fcd
 6220b9c0 603f5820 623ae028 00000000
 e187bcb0 603a2bcd 623ae000 62370010
Call Trace:
 [&amp;lt;60028f61&amp;gt;] ? vector_device_release+0x0/0x50
 [&amp;lt;60276fcd&amp;gt;] device_release+0x70/0xba
 [&amp;lt;603a2bcd&amp;gt;] kobject_put+0xba/0xe7
 [&amp;lt;60277265&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;60281266&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;60281e5f&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;60029422&amp;gt;] vector_remove+0x52/0x58
 [&amp;lt;60031316&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;600310c8&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;603b19f4&amp;gt;] ? strlen+0x0/0x15
 [&amp;lt;60066611&amp;gt;] ? __dequeue_entity+0x1a9/0x206
 [&amp;lt;600666a7&amp;gt;] ? set_next_entity+0x39/0x63
 [&amp;lt;6006666e&amp;gt;] ? set_next_enti…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-53181</guid>
    </item>
    <item>
      <title>GHSA-88cq-qg58-jw23</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-88cq-qg58-jw23</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;um: vector: 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 vector_device instance. Otherwise, removing a vector device
will result in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:vector_device_release+0xf/0x50
RSP: 00000000e187bc40  EFLAGS: 00010202
RAX: 0000000060028f61 RBX: 00000000600f1baf RCX: 00000000620074e0
RDX: 000000006220b9c0 RSI: 0000000060551c80 RDI: 0000000000000000
RBP: 00000000e187bc50 R08: 00000000603ad594 R09: 00000000e187bb70
R10: 000000000000135a R11: 00000000603ad422 R12: 00000000623ae028
R13: 000000006287a200 R14: 0000000062006d30 R15: 00000000623700b6
Kernel panic - not syncing: Segfault with no mm
CPU: 0 UID: 0 PID: 16 Comm: kworker/0:1 Not tainted 6.12.0-rc6-g59b723cd2adb #1
Workqueue: events mc_work_proc
Stack:
 60028f61 623ae028 e187bc80 60276fcd
 6220b9c0 603f5820 623ae028 00000000
 e187bcb0 603a2bcd 623ae000 62370010
Call Trace:
 [&amp;lt;60028f61&amp;gt;] ? vector_device_release+0x0/0x50
 [&amp;lt;60276fcd&amp;gt;] device_release+0x70/0xba
 [&amp;lt;603a2bcd&amp;gt;] kobject_put+0xba/0xe7
 [&amp;lt;60277265&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;60281266&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;60281e5f&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;60029422&amp;gt;] vector_remove+0x52/0x58
 [&amp;lt;60031316&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;600310c8&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;603b19f4&amp;gt;] ? strlen+0x0/0x15
 [&amp;lt;60066611&amp;gt;] ? __dequeue_entity+0x1a9/0x206
 [&amp;lt;600666a7&amp;gt;] ? set_next_entity+0x39/0x63
 [&amp;lt;6006666e&amp;gt;] ? set_next_enti…&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: vector: 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 vector_device instance. Otherwise, removing a vector device
will result in a crash:&lt;/p&gt;
&lt;p&gt;RIP: 0033:vector_device_release+0xf/0x50
RSP: 00000000e187bc40  EFLAGS: 00010202
RAX: 0000000060028f61 RBX: 00000000600f1baf RCX: 00000000620074e0
RDX: 000000006220b9c0 RSI: 0000000060551c80 RDI: 0000000000000000
RBP: 00000000e187bc50 R08: 00000000603ad594 R09: 00000000e187bb70
R10: 000000000000135a R11: 00000000603ad422 R12: 00000000623ae028
R13: 000000006287a200 R14: 0000000062006d30 R15: 00000000623700b6
Kernel panic - not syncing: Segfault with no mm
CPU: 0 UID: 0 PID: 16 Comm: kworker/0:1 Not tainted 6.12.0-rc6-g59b723cd2adb #1
Workqueue: events mc_work_proc
Stack:
 60028f61 623ae028 e187bc80 60276fcd
 6220b9c0 603f5820 623ae028 00000000
 e187bcb0 603a2bcd 623ae000 62370010
Call Trace:
 [&amp;lt;60028f61&amp;gt;] ? vector_device_release+0x0/0x50
 [&amp;lt;60276fcd&amp;gt;] device_release+0x70/0xba
 [&amp;lt;603a2bcd&amp;gt;] kobject_put+0xba/0xe7
 [&amp;lt;60277265&amp;gt;] put_device+0x19/0x1c
 [&amp;lt;60281266&amp;gt;] platform_device_put+0x26/0x29
 [&amp;lt;60281e5f&amp;gt;] platform_device_unregister+0x2c/0x2e
 [&amp;lt;60029422&amp;gt;] vector_remove+0x52/0x58
 [&amp;lt;60031316&amp;gt;] ? mconsole_reply+0x0/0x50
 [&amp;lt;600310c8&amp;gt;] mconsole_remove+0x160/0x1cc
 [&amp;lt;603b19f4&amp;gt;] ? strlen+0x0/0x15
 [&amp;lt;60066611&amp;gt;] ? __dequeue_entity+0x1a9/0x206
 [&amp;lt;600666a7&amp;gt;] ? set_next_entity+0x39/0x63
 [&amp;lt;6006666e&amp;gt;] ? set_next_enti…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-88cq-qg58-jw23</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-1286 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1286</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1286</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-53181</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53181</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: vector: Do not use drvdata in release The drvdata is not available in release. Let&amp;#39;s just use container_of() to get the vector_device instance. Otherwise, removing a vector device will result in a crash: RIP: 0033:vector_device_release+0xf/0x50 RSP: 00000000e187bc40  EFLAGS: 00010202 RAX: 0000000060028f61 RBX: 00000000600f1baf RCX: 00000000620074e0 RDX: 000000006220b9c0 RSI: 0000000060551c80 RDI: 0000000000000000 RBP: 00000000e187bc50 R08: 00000000603ad594 R09: 00000000e187bb70 R10: 000000000000135a R11: 00000000603ad422 R12: 00000000623ae028 R13: 000000006287a200 R14: 0000000062006d30 R15: 00000000623700b6 Kernel panic - not syncing: Segfault with no mm CPU: 0 UID: 0 PID: 16 Comm: kworker/0:1 Not tainted 6.12.0-rc6-g59b723cd2adb #1 Workqueue: events mc_work_proc Stack:  60028f61 623ae028 e187bc80 60276fcd  6220b9c0 603f5820 623ae028 00000000  e187bcb0 603a2bcd 623ae000 62370010 Call Trace:  [&amp;lt;60028f61&amp;gt;] ? vector_device_release+0x0/0x50  [&amp;lt;60276fcd&amp;gt;] device_release+0x70/0xba  [&amp;lt;603a2bcd&amp;gt;] kobject_put+0xba/0xe7  [&amp;lt;60277265&amp;gt;] put_device+0x19/0x1c  [&amp;lt;60281266&amp;gt;] platform_device_put+0x26/0x29  [&amp;lt;60281e5f&amp;gt;] platform_device_unregister+0x2c/0x2e  [&amp;lt;60029422&amp;gt;] vector_remove+0x52/0x58  [&amp;lt;60031316&amp;gt;] ? mconsole_reply+0x0/0x50  [&amp;lt;600310c8&amp;gt;] mconsole_remove+0x160/0x1cc  [&amp;lt;603b19f4&amp;gt;] ? strlen+0x0/0x15  [&amp;lt;60066611&amp;gt;] ? __dequeue_entity+0x1a9/0x206  [&amp;lt;600666a7&amp;gt;] ? set_next_entity+0x39/0x63  [&amp;lt;6006666e&amp;gt;] ? set_next_entity+…&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: vector: Do not use drvdata in release The drvdata is not available in release. Let&amp;#39;s just use container_of() to get the vector_device instance. Otherwise, removing a vector device will result in a crash: RIP: 0033:vector_device_release+0xf/0x50 RSP: 00000000e187bc40  EFLAGS: 00010202 RAX: 0000000060028f61 RBX: 00000000600f1baf RCX: 00000000620074e0 RDX: 000000006220b9c0 RSI: 0000000060551c80 RDI: 0000000000000000 RBP: 00000000e187bc50 R08: 00000000603ad594 R09: 00000000e187bb70 R10: 000000000000135a R11: 00000000603ad422 R12: 00000000623ae028 R13: 000000006287a200 R14: 0000000062006d30 R15: 00000000623700b6 Kernel panic - not syncing: Segfault with no mm CPU: 0 UID: 0 PID: 16 Comm: kworker/0:1 Not tainted 6.12.0-rc6-g59b723cd2adb #1 Workqueue: events mc_work_proc Stack:  60028f61 623ae028 e187bc80 60276fcd  6220b9c0 603f5820 623ae028 00000000  e187bcb0 603a2bcd 623ae000 62370010 Call Trace:  [&amp;lt;60028f61&amp;gt;] ? vector_device_release+0x0/0x50  [&amp;lt;60276fcd&amp;gt;] device_release+0x70/0xba  [&amp;lt;603a2bcd&amp;gt;] kobject_put+0xba/0xe7  [&amp;lt;60277265&amp;gt;] put_device+0x19/0x1c  [&amp;lt;60281266&amp;gt;] platform_device_put+0x26/0x29  [&amp;lt;60281e5f&amp;gt;] platform_device_unregister+0x2c/0x2e  [&amp;lt;60029422&amp;gt;] vector_remove+0x52/0x58  [&amp;lt;60031316&amp;gt;] ? mconsole_reply+0x0/0x50  [&amp;lt;600310c8&amp;gt;] mconsole_remove+0x160/0x1cc  [&amp;lt;603b19f4&amp;gt;] ? strlen+0x0/0x15  [&amp;lt;60066611&amp;gt;] ? __dequeue_entity+0x1a9/0x206  [&amp;lt;600666a7&amp;gt;] ? set_next_entity+0x39/0x63  [&amp;lt;6006666e&amp;gt;] ? set_next_entity+…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-53181</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>
