<?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 13:31:46 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:20095 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:20095</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more&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: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: exfat: fix out-of-bounds access of directory entries (CVE-2024-53147)
  * kernel: zram: fix NULL pointer in comp_algorithm_show() (CVE-2024-53222)
  * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
  * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
  * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
  * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
  * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
  * kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)
  * kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)
  * kernel: io_uring/sqpoll: zero sqd-&amp;gt;thread on tctx errors (CVE-2025-21633)
  * kernel: ipvlan: Fix use-after-free in ipvlan_get_iflink(). (CVE-2025-21652)
  * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
  * kernel: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (CVE-2025-21655)
  * kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled (CVE-2024-57941)
  * kernel: netfs: Fix ceph copy to cache…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more&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: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: exfat: fix out-of-bounds access of directory entries (CVE-2024-53147)
  * kernel: zram: fix NULL pointer in comp_algorithm_show() (CVE-2024-53222)
  * kernel: nfsd: release svc_expkey/svc_export with rcu_work (CVE-2024-53216)
  * kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl (CVE-2024-56662)
  * kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors (CVE-2024-56675)
  * kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY (CVE-2024-56690)
  * kernel: igb: Fix potential invalid memory access in igb_init_module() (CVE-2024-52332)
  * kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK (CVE-2024-57901)
  * kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK (CVE-2024-57902)
  * kernel: io_uring/sqpoll: zero sqd-&amp;gt;thread on tctx errors (CVE-2025-21633)
  * kernel: ipvlan: Fix use-after-free in ipvlan_get_iflink(). (CVE-2025-21652)
  * kernel: sched: sch_cake: add bounds checks to host bulk flow fairness counts (CVE-2025-21647)
  * kernel: io_uring/eventfd: ensure io_eventfd_signal() defers another RCU period (CVE-2025-21655)
  * kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled (CVE-2024-57941)
  * kernel: netfs: Fix ceph copy to cache…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:20095</guid>
    </item>
    <item>
      <title>bdu:2025-03895</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03895</link>
      <description>bdu:2025-03895</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03895</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-57984</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-57984</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-57984</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0625 — De multiples vulnérabilités ont été découvertes dans Ubuntu Ubuntu. Certaines d'entre elles permettent à un attaquant d…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0625</link>
      <description>certfr-2025-avi-0625</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0625</guid>
    </item>
    <item>
      <title>EUVD-2026-346574</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346574</link>
      <description>EUVD-2026-346574</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346574</guid>
    </item>
    <item>
      <title>fkie_cve-2024-57984</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-57984</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition&lt;/p&gt;
&lt;p&gt;In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with
dw_i3c_hj_work. And dw_i3c_master_irq_handler can call
dw_i3c_master_irq_handle_ibis function to start the work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call dw_i3c_common_remove to
make cleanup, it will free master-&amp;gt;base through i3c_master_unregister
while the work mentioned above will be used. The sequence of operations
that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| dw_i3c_hj_work
dw_i3c_common_remove                 |
i3c_master_unregister(&amp;amp;master-&amp;gt;base) |
device_unregister(&amp;amp;master-&amp;gt;dev)      |
device_release                       |
//free master-&amp;gt;base                  |
                                     | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)
                                     | //use master-&amp;gt;base&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in dw_i3c_common_remove.&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;i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition&lt;/p&gt;
&lt;p&gt;In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with
dw_i3c_hj_work. And dw_i3c_master_irq_handler can call
dw_i3c_master_irq_handle_ibis function to start the work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call dw_i3c_common_remove to
make cleanup, it will free master-&amp;gt;base through i3c_master_unregister
while the work mentioned above will be used. The sequence of operations
that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| dw_i3c_hj_work
dw_i3c_common_remove                 |
i3c_master_unregister(&amp;amp;master-&amp;gt;base) |
device_unregister(&amp;amp;master-&amp;gt;dev)      |
device_release                       |
//free master-&amp;gt;base                  |
                                     | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)
                                     | //use master-&amp;gt;base&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in dw_i3c_common_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-57984</guid>
    </item>
    <item>
      <title>GHSA-wqcr-wj43-4gg7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wqcr-wj43-4gg7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition&lt;/p&gt;
&lt;p&gt;In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with
dw_i3c_hj_work. And dw_i3c_master_irq_handler can call
dw_i3c_master_irq_handle_ibis function to start the work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call dw_i3c_common_remove to
make cleanup, it will free master-&amp;gt;base through i3c_master_unregister
while the work mentioned above will be used. The sequence of operations
that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| dw_i3c_hj_work
dw_i3c_common_remove                 |
i3c_master_unregister(&amp;amp;master-&amp;gt;base) |
device_unregister(&amp;amp;master-&amp;gt;dev)      |
device_release                       |
//free master-&amp;gt;base                  |
                                     | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)
                                     | //use master-&amp;gt;base&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in dw_i3c_common_remove.&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;i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition&lt;/p&gt;
&lt;p&gt;In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with
dw_i3c_hj_work. And dw_i3c_master_irq_handler can call
dw_i3c_master_irq_handle_ibis function to start the work.&lt;/p&gt;
&lt;p&gt;If we remove the module which will call dw_i3c_common_remove to
make cleanup, it will free master-&amp;gt;base through i3c_master_unregister
while the work mentioned above will be used. The sequence of operations
that may lead to a UAF bug is as follows:&lt;/p&gt;
&lt;p&gt;CPU0                                      CPU1&lt;/p&gt;
&lt;p&gt;| dw_i3c_hj_work
dw_i3c_common_remove                 |
i3c_master_unregister(&amp;amp;master-&amp;gt;base) |
device_unregister(&amp;amp;master-&amp;gt;dev)      |
device_release                       |
//free master-&amp;gt;base                  |
                                     | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)
                                     | //use master-&amp;gt;base&lt;/p&gt;
&lt;p&gt;Fix it by ensuring that the work is canceled before proceeding with
the cleanup in dw_i3c_common_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wqcr-wj43-4gg7</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-57984 — i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-57984</link>
      <description>msrc_CVE-2024-57984</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-57984</guid>
    </item>
    <item>
      <title>RHSA-2025:20095 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:20095</link>
      <description>&lt;p&gt;microcode_ctl: From CVEorg collector kernel: information leak via transient execution vulnerability in some AMD processors kernel: transient execution vulnerability in some AMD processors kernel: drm/xe/tracing: Fix a potential TP_printk UAF kernel: igb: Fix potential invalid memory access in igb_init_module() kernel: exfat: fix out-of-bounds access of directory entries kernel: nfsd: release svc_expkey/svc_export with rcu_work kernel: zram: fix NULL pointer in comp_algorithm_show() kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled kernel: netfs: Fix ceph copy to cache on write-begin kernel: memcg: fix soft lockup in the OOM process kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts kernel: xfrm: state: fix out-of-bounds read during lookup kernel: i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections kernel: Bluet…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;microcode_ctl: From CVEorg collector kernel: information leak via transient execution vulnerability in some AMD processors kernel: transient execution vulnerability in some AMD processors kernel: drm/xe/tracing: Fix a potential TP_printk UAF kernel: igb: Fix potential invalid memory access in igb_init_module() kernel: exfat: fix out-of-bounds access of directory entries kernel: nfsd: release svc_expkey/svc_export with rcu_work kernel: zram: fix NULL pointer in comp_algorithm_show() kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) kernel: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() kernel: acpi: nfit: vmalloc-out-of-bounds Read in acpi_nfit_ctl kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors kernel: crypto: pcrypt - Call crypto layer directly when padata_do_parallel() return -EBUSY kernel: af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK kernel: af_packet: fix vlan_get_tci() vs MSG_PEEK kernel: netfs: Fix the (non-)cancellation of copy when cache is temporarily disabled kernel: netfs: Fix ceph copy to cache on write-begin kernel: memcg: fix soft lockup in the OOM process kernel: usb: xhci: Fix NULL pointer dereference on certain command aborts kernel: xfrm: state: fix out-of-bounds read during lookup kernel: i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition kernel: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections kernel: Bluet…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:20095</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-57984</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57984</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with dw_i3c_hj_work. And dw_i3c_master_irq_handler can call dw_i3c_master_irq_handle_ibis function to start the work. If we remove the module which will call dw_i3c_common_remove to make cleanup, it will free master-&amp;gt;base through i3c_master_unregister while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0                                      CPU1                                      | dw_i3c_hj_work dw_i3c_common_remove                 | i3c_master_unregister(&amp;amp;master-&amp;gt;base) | device_unregister(&amp;amp;master-&amp;gt;dev)      | device_release                       | //free master-&amp;gt;base                  |                                      | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)                                      | //use master-&amp;gt;base Fix it by ensuring that the work is canceled before proceeding with the cleanup in dw_i3c_common_remove.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: i3c: dw: Fix use-after-free in dw_i3c_master driver due to race condition In dw_i3c_common_probe, &amp;amp;master-&amp;gt;hj_work is bound with dw_i3c_hj_work. And dw_i3c_master_irq_handler can call dw_i3c_master_irq_handle_ibis function to start the work. If we remove the module which will call dw_i3c_common_remove to make cleanup, it will free master-&amp;gt;base through i3c_master_unregister while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0                                      CPU1                                      | dw_i3c_hj_work dw_i3c_common_remove                 | i3c_master_unregister(&amp;amp;master-&amp;gt;base) | device_unregister(&amp;amp;master-&amp;gt;dev)      | device_release                       | //free master-&amp;gt;base                  |                                      | i3c_master_do_daa(&amp;amp;master-&amp;gt;base)                                      | //use master-&amp;gt;base Fix it by ensuring that the work is canceled before proceeding with the cleanup in dw_i3c_common_remove.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-57984</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0453 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0453</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0453</guid>
    </item>
  </channel>
</rss>
