<?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 10:55:08 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:15005 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:15005</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: udp: Fix memory accounting leak. (CVE-2025-22058)
  * kernel: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (CVE-2025-37823)
  * kernel: ext4: only dirty folios when data journaling regular files (CVE-2025-38220)
  * kernel: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction (CVE-2025-38211)
  * kernel: tipc: Fix use-after-free in tipc_conn_close() (CVE-2025-38464)
  * kernel: vsock: Fix transport_* TOCTOU (CVE-2025-38461)
  * kernel: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (CVE-2025-38472)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: udp: Fix memory accounting leak. (CVE-2025-22058)
  * kernel: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (CVE-2025-37823)
  * kernel: ext4: only dirty folios when data journaling regular files (CVE-2025-38220)
  * kernel: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction (CVE-2025-38211)
  * kernel: tipc: Fix use-after-free in tipc_conn_close() (CVE-2025-38464)
  * kernel: vsock: Fix transport_* TOCTOU (CVE-2025-38461)
  * kernel: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry (CVE-2025-38472)&lt;/p&gt;
&lt;p&gt;For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:15005</guid>
    </item>
    <item>
      <title>bdu:2025-15216</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15216</link>
      <description>bdu:2025-15216</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15216</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38211</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38211</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-38211</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>EUVD-2026-346964</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346964</link>
      <description>EUVD-2026-346964</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346964</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38211</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38211</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction&lt;/p&gt;
&lt;p&gt;The commit 59c68ac31e15 (&amp;#34;iw_cm: free cm_id resources on the last
deref&amp;#34;) simplified cm_id resource management by freeing cm_id once all
references to the cm_id were removed. The references are removed either
upon completion of iw_cm event handlers or when the application destroys
the cm_id. This commit introduced the use-after-free condition where
cm_id_private object could still be in use by event handler works during
the destruction of cm_id. The commit aee2424246f9 (&amp;#34;RDMA/iwcm: Fix a
use-after-free related to destroying CM IDs&amp;#34;) addressed this use-after-
free by flushing all pending works at the cm_id destruction.&lt;/p&gt;
&lt;p&gt;However, still another use-after-free possibility remained. It happens
with the work objects allocated for each cm_id_priv within
alloc_work_entries() during cm_id creation, and subsequently freed in
dealloc_work_entries() once all references to the cm_id are removed.
If the cm_id&amp;#39;s last reference is decremented in the event handler work,
the work object for the work itself gets removed, and causes the use-
after-free BUG below:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250
  Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091&lt;/p&gt;
&lt;p&gt;CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS…&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/iwcm: Fix use-after-free of work objects after cm_id destruction&lt;/p&gt;
&lt;p&gt;The commit 59c68ac31e15 (&amp;#34;iw_cm: free cm_id resources on the last
deref&amp;#34;) simplified cm_id resource management by freeing cm_id once all
references to the cm_id were removed. The references are removed either
upon completion of iw_cm event handlers or when the application destroys
the cm_id. This commit introduced the use-after-free condition where
cm_id_private object could still be in use by event handler works during
the destruction of cm_id. The commit aee2424246f9 (&amp;#34;RDMA/iwcm: Fix a
use-after-free related to destroying CM IDs&amp;#34;) addressed this use-after-
free by flushing all pending works at the cm_id destruction.&lt;/p&gt;
&lt;p&gt;However, still another use-after-free possibility remained. It happens
with the work objects allocated for each cm_id_priv within
alloc_work_entries() during cm_id creation, and subsequently freed in
dealloc_work_entries() once all references to the cm_id are removed.
If the cm_id&amp;#39;s last reference is decremented in the event handler work,
the work object for the work itself gets removed, and causes the use-
after-free BUG below:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250
  Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091&lt;/p&gt;
&lt;p&gt;CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38211</guid>
    </item>
    <item>
      <title>GHSA-wcw7-g3wh-rxf7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wcw7-g3wh-rxf7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction&lt;/p&gt;
&lt;p&gt;The commit 59c68ac31e15 (&amp;#34;iw_cm: free cm_id resources on the last
deref&amp;#34;) simplified cm_id resource management by freeing cm_id once all
references to the cm_id were removed. The references are removed either
upon completion of iw_cm event handlers or when the application destroys
the cm_id. This commit introduced the use-after-free condition where
cm_id_private object could still be in use by event handler works during
the destruction of cm_id. The commit aee2424246f9 (&amp;#34;RDMA/iwcm: Fix a
use-after-free related to destroying CM IDs&amp;#34;) addressed this use-after-
free by flushing all pending works at the cm_id destruction.&lt;/p&gt;
&lt;p&gt;However, still another use-after-free possibility remained. It happens
with the work objects allocated for each cm_id_priv within
alloc_work_entries() during cm_id creation, and subsequently freed in
dealloc_work_entries() once all references to the cm_id are removed.
If the cm_id&amp;#39;s last reference is decremented in the event handler work,
the work object for the work itself gets removed, and causes the use-
after-free BUG below:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250
  Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091&lt;/p&gt;
&lt;p&gt;CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS…&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/iwcm: Fix use-after-free of work objects after cm_id destruction&lt;/p&gt;
&lt;p&gt;The commit 59c68ac31e15 (&amp;#34;iw_cm: free cm_id resources on the last
deref&amp;#34;) simplified cm_id resource management by freeing cm_id once all
references to the cm_id were removed. The references are removed either
upon completion of iw_cm event handlers or when the application destroys
the cm_id. This commit introduced the use-after-free condition where
cm_id_private object could still be in use by event handler works during
the destruction of cm_id. The commit aee2424246f9 (&amp;#34;RDMA/iwcm: Fix a
use-after-free related to destroying CM IDs&amp;#34;) addressed this use-after-
free by flushing all pending works at the cm_id destruction.&lt;/p&gt;
&lt;p&gt;However, still another use-after-free possibility remained. It happens
with the work objects allocated for each cm_id_priv within
alloc_work_entries() during cm_id creation, and subsequently freed in
dealloc_work_entries() once all references to the cm_id are removed.
If the cm_id&amp;#39;s last reference is decremented in the event handler work,
the work object for the work itself gets removed, and causes the use-
after-free BUG below:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250
  Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091&lt;/p&gt;
&lt;p&gt;CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary)
  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wcw7-g3wh-rxf7</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-38211 — RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-38211</link>
      <description>msrc_CVE-2025-38211</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-38211</guid>
    </item>
    <item>
      <title>OESA-2025-2054 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2054</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;drm/vkms: Fix use after free and double free on init error&lt;/p&gt;
&lt;p&gt;If the driver initialization fails, the vkms_exit() function might
access an uninitialized or freed default_config pointer and it might
double free it.&lt;/p&gt;
&lt;p&gt;Fix both possible errors by initializing default_config only when the
driver initialization succeeded.(CVE-2025-22097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: at76c50x: fix use after free access in at76_disconnect&lt;/p&gt;
&lt;p&gt;The memory pointed to by priv is freed at the end of at76_delete_device
function (using ieee80211_free_hw). But the code then accesses the udev
field of the freed object to put the USB device. This may also lead to a
memory leak of the usb device. Fix this by using udev from interface.(CVE-2025-37796)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;codel: remove sch-&amp;amp;gt;q.qlen check before qdisc_tree_reduce_backlog()&lt;/p&gt;
&lt;p&gt;After making all -&amp;amp;gt;qlen_notify() callbacks idempotent, now it is safe to
remove the check of qlen!=0 from both fq_codel_dequeue() and
codel_qdisc_dequeue().(CVE-2025-37798)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net_sched: qfq: Fix double list add in class with netem as child qdisc&lt;/p&gt;
&lt;p&gt;As described in Gerrard&amp;amp;apos;s report [1], there are use cases where a netem
child qdisc will make the parent qdisc&amp;amp;apos;s enqueue…&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;drm/vkms: Fix use after free and double free on init error&lt;/p&gt;
&lt;p&gt;If the driver initialization fails, the vkms_exit() function might
access an uninitialized or freed default_config pointer and it might
double free it.&lt;/p&gt;
&lt;p&gt;Fix both possible errors by initializing default_config only when the
driver initialization succeeded.(CVE-2025-22097)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: at76c50x: fix use after free access in at76_disconnect&lt;/p&gt;
&lt;p&gt;The memory pointed to by priv is freed at the end of at76_delete_device
function (using ieee80211_free_hw). But the code then accesses the udev
field of the freed object to put the USB device. This may also lead to a
memory leak of the usb device. Fix this by using udev from interface.(CVE-2025-37796)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;codel: remove sch-&amp;amp;gt;q.qlen check before qdisc_tree_reduce_backlog()&lt;/p&gt;
&lt;p&gt;After making all -&amp;amp;gt;qlen_notify() callbacks idempotent, now it is safe to
remove the check of qlen!=0 from both fq_codel_dequeue() and
codel_qdisc_dequeue().(CVE-2025-37798)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net_sched: qfq: Fix double list add in class with netem as child qdisc&lt;/p&gt;
&lt;p&gt;As described in Gerrard&amp;amp;apos;s report [1], there are use cases where a netem
child qdisc will make the parent qdisc&amp;amp;apos;s enqueue…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2054</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>RHSA-2025:15005 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:15005</link>
      <description>&lt;p&gt;kernel: udp: Fix memory accounting leak. kernel: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too kernel: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction kernel: ext4: only dirty folios when data journaling regular files kernel: vsock: Fix transport_* TOCTOU kernel: tipc: Fix use-after-free in tipc_conn_close() kernel: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: udp: Fix memory accounting leak. kernel: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too kernel: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction kernel: ext4: only dirty folios when data journaling regular files kernel: vsock: Fix transport_* TOCTOU kernel: tipc: Fix use-after-free in tipc_conn_close() kernel: netfilter: nf_conntrack: fix crash due to removal of uninitialised entry&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:15005</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02846-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02846-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:02846-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38211</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38211</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction The commit 59c68ac31e15 (&amp;#34;iw_cm: free cm_id resources on the last deref&amp;#34;) simplified cm_id resource management by freeing cm_id once all references to the cm_id were removed. The references are removed either upon completion of iw_cm event handlers or when the application destroys the cm_id. This commit introduced the use-after-free condition where cm_id_private object could still be in use by event handler works during the destruction of cm_id. The commit aee2424246f9 (&amp;#34;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs&amp;#34;) addressed this use-after- free by flushing all pending works at the cm_id destruction. However, still another use-after-free possibility remained. It happens with the work objects allocated for each cm_id_priv within alloc_work_entries() during cm_id creation, and subsequently freed in dealloc_work_entries() once all references to the cm_id are removed. If the cm_id&amp;#39;s last reference is decremented in the event handler work, the work object for the work itself gets removed, and causes the use- after-free BUG below:   BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250   Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091   CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary)   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: RDMA/iwcm: Fix use-after-free of work objects after cm_id destruction The commit 59c68ac31e15 (&amp;#34;iw_cm: free cm_id resources on the last deref&amp;#34;) simplified cm_id resource management by freeing cm_id once all references to the cm_id were removed. The references are removed either upon completion of iw_cm event handlers or when the application destroys the cm_id. This commit introduced the use-after-free condition where cm_id_private object could still be in use by event handler works during the destruction of cm_id. The commit aee2424246f9 (&amp;#34;RDMA/iwcm: Fix a use-after-free related to destroying CM IDs&amp;#34;) addressed this use-after- free by flushing all pending works at the cm_id destruction. However, still another use-after-free possibility remained. It happens with the work objects allocated for each cm_id_priv within alloc_work_entries() during cm_id creation, and subsequently freed in dealloc_work_entries() once all references to the cm_id are removed. If the cm_id&amp;#39;s last reference is decremented in the event handler work, the work object for the work itself gets removed, and causes the use- after-free BUG below:   BUG: KASAN: slab-use-after-free in __pwq_activate_work+0x1ff/0x250   Read of size 8 at addr ffff88811f9cf800 by task kworker/u16:1/147091   CPU: 2 UID: 0 PID: 147091 Comm: kworker/u16:1 Not tainted 6.15.0-rc2+ #27 PREEMPT(voluntary)   Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38211</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1465 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1465</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 spezifizierte 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 spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1465</guid>
    </item>
  </channel>
</rss>
