<?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>Sun, 04 Oct 2026 06:12:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07797</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07797</link>
      <description>bdu:2025-07797</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07797</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56545</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-56545</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-367452</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367452</link>
      <description>EUVD-2026-367452</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367452</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56545</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56545</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hyperv: streamline driver probe to avoid devres issues&lt;/p&gt;
&lt;p&gt;It was found that unloading &amp;#39;hid_hyperv&amp;#39; module results in a devres
complaint:&lt;/p&gt;
&lt;p&gt;...
 hv_vmbus: unregistering driver hid_hyperv
 ------------[ cut here ]------------
 WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  ? devres_release_group+0x1f2/0x2c0
  ? __warn+0xd1/0x1c0
  ? devres_release_group+0x1f2/0x2c0
  ? report_bug+0x32a/0x3c0
  ? handle_bug+0x53/0xa0
  ? exc_invalid_op+0x18/0x50
  ? asm_exc_invalid_op+0x1a/0x20
  ? devres_release_group+0x1f2/0x2c0
  ? devres_release_group+0x90/0x2c0
  ? rcu_is_watching+0x15/0xb0
  ? __pfx_devres_release_group+0x10/0x10
  hid_device_remove+0xf5/0x220
  device_release_driver_internal+0x371/0x540
  ? klist_put+0xf3/0x170
  bus_remove_device+0x1f1/0x3f0
  device_del+0x33f/0x8c0
  ? __pfx_device_del+0x10/0x10
  ? cleanup_srcu_struct+0x337/0x500
  hid_destroy_device+0xc8/0x130
  mousevsc_remove+0xd2/0x1d0 [hid_hyperv]
  device_release_driver_internal+0x371/0x540
  driver_detach+0xc5/0x180
  bus_remove_driver+0x11e/0x2a0
  ? __mutex_unlock_slowpath+0x160/0x5e0
  vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus]
  ...&lt;/p&gt;
&lt;p&gt;And the issue seems to be that the corresponding devres group is not
allocated. Normally, devres_open_group() is called from
__hid_device_probe() but Hyper-V HID driver overrides &amp;#39;hid_dev-&amp;gt;driver&amp;#39;
with &amp;#39;mousevsc_hid_driver&amp;#39; stub and ba…&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;HID: hyperv: streamline driver probe to avoid devres issues&lt;/p&gt;
&lt;p&gt;It was found that unloading &amp;#39;hid_hyperv&amp;#39; module results in a devres
complaint:&lt;/p&gt;
&lt;p&gt;...
 hv_vmbus: unregistering driver hid_hyperv
 ------------[ cut here ]------------
 WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  ? devres_release_group+0x1f2/0x2c0
  ? __warn+0xd1/0x1c0
  ? devres_release_group+0x1f2/0x2c0
  ? report_bug+0x32a/0x3c0
  ? handle_bug+0x53/0xa0
  ? exc_invalid_op+0x18/0x50
  ? asm_exc_invalid_op+0x1a/0x20
  ? devres_release_group+0x1f2/0x2c0
  ? devres_release_group+0x90/0x2c0
  ? rcu_is_watching+0x15/0xb0
  ? __pfx_devres_release_group+0x10/0x10
  hid_device_remove+0xf5/0x220
  device_release_driver_internal+0x371/0x540
  ? klist_put+0xf3/0x170
  bus_remove_device+0x1f1/0x3f0
  device_del+0x33f/0x8c0
  ? __pfx_device_del+0x10/0x10
  ? cleanup_srcu_struct+0x337/0x500
  hid_destroy_device+0xc8/0x130
  mousevsc_remove+0xd2/0x1d0 [hid_hyperv]
  device_release_driver_internal+0x371/0x540
  driver_detach+0xc5/0x180
  bus_remove_driver+0x11e/0x2a0
  ? __mutex_unlock_slowpath+0x160/0x5e0
  vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus]
  ...&lt;/p&gt;
&lt;p&gt;And the issue seems to be that the corresponding devres group is not
allocated. Normally, devres_open_group() is called from
__hid_device_probe() but Hyper-V HID driver overrides &amp;#39;hid_dev-&amp;gt;driver&amp;#39;
with &amp;#39;mousevsc_hid_driver&amp;#39; stub and ba…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56545</guid>
    </item>
    <item>
      <title>GHSA-r47r-3q5h-27v7</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r47r-3q5h-27v7</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: hyperv: streamline driver probe to avoid devres issues&lt;/p&gt;
&lt;p&gt;It was found that unloading &amp;#39;hid_hyperv&amp;#39; module results in a devres
complaint:&lt;/p&gt;
&lt;p&gt;...
 hv_vmbus: unregistering driver hid_hyperv
 ------------[ cut here ]------------
 WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  ? devres_release_group+0x1f2/0x2c0
  ? __warn+0xd1/0x1c0
  ? devres_release_group+0x1f2/0x2c0
  ? report_bug+0x32a/0x3c0
  ? handle_bug+0x53/0xa0
  ? exc_invalid_op+0x18/0x50
  ? asm_exc_invalid_op+0x1a/0x20
  ? devres_release_group+0x1f2/0x2c0
  ? devres_release_group+0x90/0x2c0
  ? rcu_is_watching+0x15/0xb0
  ? __pfx_devres_release_group+0x10/0x10
  hid_device_remove+0xf5/0x220
  device_release_driver_internal+0x371/0x540
  ? klist_put+0xf3/0x170
  bus_remove_device+0x1f1/0x3f0
  device_del+0x33f/0x8c0
  ? __pfx_device_del+0x10/0x10
  ? cleanup_srcu_struct+0x337/0x500
  hid_destroy_device+0xc8/0x130
  mousevsc_remove+0xd2/0x1d0 [hid_hyperv]
  device_release_driver_internal+0x371/0x540
  driver_detach+0xc5/0x180
  bus_remove_driver+0x11e/0x2a0
  ? __mutex_unlock_slowpath+0x160/0x5e0
  vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus]
  ...&lt;/p&gt;
&lt;p&gt;And the issue seems to be that the corresponding devres group is not
allocated. Normally, devres_open_group() is called from
__hid_device_probe() but Hyper-V HID driver overrides &amp;#39;hid_dev-&amp;gt;driver&amp;#39;
with &amp;#39;mousevsc_hid_driver&amp;#39; stub and ba…&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;HID: hyperv: streamline driver probe to avoid devres issues&lt;/p&gt;
&lt;p&gt;It was found that unloading &amp;#39;hid_hyperv&amp;#39; module results in a devres
complaint:&lt;/p&gt;
&lt;p&gt;...
 hv_vmbus: unregistering driver hid_hyperv
 ------------[ cut here ]------------
 WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0
 ...
 Call Trace:
  &amp;lt;TASK&amp;gt;
  ? devres_release_group+0x1f2/0x2c0
  ? __warn+0xd1/0x1c0
  ? devres_release_group+0x1f2/0x2c0
  ? report_bug+0x32a/0x3c0
  ? handle_bug+0x53/0xa0
  ? exc_invalid_op+0x18/0x50
  ? asm_exc_invalid_op+0x1a/0x20
  ? devres_release_group+0x1f2/0x2c0
  ? devres_release_group+0x90/0x2c0
  ? rcu_is_watching+0x15/0xb0
  ? __pfx_devres_release_group+0x10/0x10
  hid_device_remove+0xf5/0x220
  device_release_driver_internal+0x371/0x540
  ? klist_put+0xf3/0x170
  bus_remove_device+0x1f1/0x3f0
  device_del+0x33f/0x8c0
  ? __pfx_device_del+0x10/0x10
  ? cleanup_srcu_struct+0x337/0x500
  hid_destroy_device+0xc8/0x130
  mousevsc_remove+0xd2/0x1d0 [hid_hyperv]
  device_release_driver_internal+0x371/0x540
  driver_detach+0xc5/0x180
  bus_remove_driver+0x11e/0x2a0
  ? __mutex_unlock_slowpath+0x160/0x5e0
  vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus]
  ...&lt;/p&gt;
&lt;p&gt;And the issue seems to be that the corresponding devres group is not
allocated. Normally, devres_open_group() is called from
__hid_device_probe() but Hyper-V HID driver overrides &amp;#39;hid_dev-&amp;gt;driver&amp;#39;
with &amp;#39;mousevsc_hid_driver&amp;#39; stub and ba…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r47r-3q5h-27v7</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>UBUNTU-CVE-2024-56545</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: hyperv: streamline driver probe to avoid devres issues It was found that unloading &amp;#39;hid_hyperv&amp;#39; module results in a devres complaint:  ...  hv_vmbus: unregistering driver hid_hyperv  ------------[ cut here ]------------  WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0  ...  Call Trace:   &amp;lt;TASK&amp;gt;   ? devres_release_group+0x1f2/0x2c0   ? __warn+0xd1/0x1c0   ? devres_release_group+0x1f2/0x2c0   ? report_bug+0x32a/0x3c0   ? handle_bug+0x53/0xa0   ? exc_invalid_op+0x18/0x50   ? asm_exc_invalid_op+0x1a/0x20   ? devres_release_group+0x1f2/0x2c0   ? devres_release_group+0x90/0x2c0   ? rcu_is_watching+0x15/0xb0   ? __pfx_devres_release_group+0x10/0x10   hid_device_remove+0xf5/0x220   device_release_driver_internal+0x371/0x540   ? klist_put+0xf3/0x170   bus_remove_device+0x1f1/0x3f0   device_del+0x33f/0x8c0   ? __pfx_device_del+0x10/0x10   ? cleanup_srcu_struct+0x337/0x500   hid_destroy_device+0xc8/0x130   mousevsc_remove+0xd2/0x1d0 [hid_hyperv]   device_release_driver_internal+0x371/0x540   driver_detach+0xc5/0x180   bus_remove_driver+0x11e/0x2a0   ? __mutex_unlock_slowpath+0x160/0x5e0   vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus]   ... And the issue seems to be that the corresponding devres group is not allocated. Normally, devres_open_group() is called from __hid_device_probe() but Hyper-V HID driver overrides &amp;#39;hid_dev-&amp;gt;driver&amp;#39; with &amp;#39;mousevsc_hid_driver&amp;#39; stub and basica…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: HID: hyperv: streamline driver probe to avoid devres issues It was found that unloading &amp;#39;hid_hyperv&amp;#39; module results in a devres complaint:  ...  hv_vmbus: unregistering driver hid_hyperv  ------------[ cut here ]------------  WARNING: CPU: 2 PID: 3983 at drivers/base/devres.c:691 devres_release_group+0x1f2/0x2c0  ...  Call Trace:   &amp;lt;TASK&amp;gt;   ? devres_release_group+0x1f2/0x2c0   ? __warn+0xd1/0x1c0   ? devres_release_group+0x1f2/0x2c0   ? report_bug+0x32a/0x3c0   ? handle_bug+0x53/0xa0   ? exc_invalid_op+0x18/0x50   ? asm_exc_invalid_op+0x1a/0x20   ? devres_release_group+0x1f2/0x2c0   ? devres_release_group+0x90/0x2c0   ? rcu_is_watching+0x15/0xb0   ? __pfx_devres_release_group+0x10/0x10   hid_device_remove+0xf5/0x220   device_release_driver_internal+0x371/0x540   ? klist_put+0xf3/0x170   bus_remove_device+0x1f1/0x3f0   device_del+0x33f/0x8c0   ? __pfx_device_del+0x10/0x10   ? cleanup_srcu_struct+0x337/0x500   hid_destroy_device+0xc8/0x130   mousevsc_remove+0xd2/0x1d0 [hid_hyperv]   device_release_driver_internal+0x371/0x540   driver_detach+0xc5/0x180   bus_remove_driver+0x11e/0x2a0   ? __mutex_unlock_slowpath+0x160/0x5e0   vmbus_driver_unregister+0x62/0x2b0 [hv_vmbus]   ... And the issue seems to be that the corresponding devres group is not allocated. Normally, devres_open_group() is called from __hid_device_probe() but Hyper-V HID driver overrides &amp;#39;hid_dev-&amp;gt;driver&amp;#39; with &amp;#39;mousevsc_hid_driver&amp;#39; stub and basica…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56545</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>
