https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 07:11:32 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-03992 bdu:2026-03992 https://cve.radiocsirt.org/vuln/bdu:2026-03992 https://cve.radiocsirt.org/vuln/bell-cve-2025-21807 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-21807 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057 certfr-2025-avi-1057 https://cve.radiocsirt.org/vuln/certfr-2025-avi-1057 https://cve.radiocsirt.org/vuln/euvd-2026-338651 EUVD-2026-338651 https://cve.radiocsirt.org/vuln/euvd-2026-338651 https://cve.radiocsirt.org/vuln/fkie_cve-2025-21807 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix queue freeze vs limits lock order in sysfs store methods</p> <p>queue_attr_store() always freezes a device queue before calling the attribute store operation. For attributes that control queue limits, the store operation will also lock the queue limits with a call to queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may need to issue commands to a device to obtain limit values from the hardware with the queue limits locked. This creates a potential ABBA deadlock situation if a user attempts to modify a limit (thus freezing the device queue) while the device driver starts a revalidation of the device queue limits.</p> <p>Avoid such deadlock by not freezing the queue before calling the -&gt;store_limit() method in struct queue_sysfs_entry and instead use the queue_limits_commit_update_frozen helper to freeze the queue after taking the limits lock.</p> <p>This also removes taking the sysfs lock for the store_limit method as it doesn&#39;t protect anything here, but creates even more nesting. Hopefully it will go away from the actual sysfs methods entirely soon.</p> <p>(commit log adapted from a similar patch from Damien Le Moal)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix queue freeze vs limits lock order in sysfs store methods</p> <p>queue_attr_store() always freezes a device queue before calling the attribute store operation. For attributes that control queue limits, the store operation will also lock the queue limits with a call to queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may need to issue commands to a device to obtain limit values from the hardware with the queue limits locked. This creates a potential ABBA deadlock situation if a user attempts to modify a limit (thus freezing the device queue) while the device driver starts a revalidation of the device queue limits.</p> <p>Avoid such deadlock by not freezing the queue before calling the -&gt;store_limit() method in struct queue_sysfs_entry and instead use the queue_limits_commit_update_frozen helper to freeze the queue after taking the limits lock.</p> <p>This also removes taking the sysfs lock for the store_limit method as it doesn&#39;t protect anything here, but creates even more nesting. Hopefully it will go away from the actual sysfs methods entirely soon.</p> <p>(commit log adapted from a similar patch from Damien Le Moal)</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-21807 https://cve.radiocsirt.org/vuln/ghsa-cp43-x3rr-gwcc <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix queue freeze vs limits lock order in sysfs store methods</p> <p>queue_attr_store() always freezes a device queue before calling the attribute store operation. For attributes that control queue limits, the store operation will also lock the queue limits with a call to queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may need to issue commands to a device to obtain limit values from the hardware with the queue limits locked. This creates a potential ABBA deadlock situation if a user attempts to modify a limit (thus freezing the device queue) while the device driver starts a revalidation of the device queue limits.</p> <p>Avoid such deadlock by not freezing the queue before calling the -&gt;store_limit() method in struct queue_sysfs_entry and instead use the queue_limits_commit_update_frozen helper to freeze the queue after taking the limits lock.</p> <p>This also removes taking the sysfs lock for the store_limit method as it doesn&#39;t protect anything here, but creates even more nesting. Hopefully it will go away from the actual sysfs methods entirely soon.</p> <p>(commit log adapted from a similar patch from Damien Le Moal)</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix queue freeze vs limits lock order in sysfs store methods</p> <p>queue_attr_store() always freezes a device queue before calling the attribute store operation. For attributes that control queue limits, the store operation will also lock the queue limits with a call to queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may need to issue commands to a device to obtain limit values from the hardware with the queue limits locked. This creates a potential ABBA deadlock situation if a user attempts to modify a limit (thus freezing the device queue) while the device driver starts a revalidation of the device queue limits.</p> <p>Avoid such deadlock by not freezing the queue before calling the -&gt;store_limit() method in struct queue_sysfs_entry and instead use the queue_limits_commit_update_frozen helper to freeze the queue after taking the limits lock.</p> <p>This also removes taking the sysfs lock for the store_limit method as it doesn&#39;t protect anything here, but creates even more nesting. Hopefully it will go away from the actual sysfs methods entirely soon.</p> <p>(commit log adapted from a similar patch from Damien Le Moal)</p> https://cve.radiocsirt.org/vuln/ghsa-cp43-x3rr-gwcc https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21807 <p><strong>Affected:</strong> 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 75 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: block: fix queue freeze vs limits lock order in sysfs store methods queue_attr_store() always freezes a device queue before calling the attribute store operation. For attributes that control queue limits, the store operation will also lock the queue limits with a call to queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may need to issue commands to a device to obtain limit values from the hardware with the queue limits locked. This creates a potential ABBA deadlock situation if a user attempts to modify a limit (thus freezing the device queue) while the device driver starts a revalidation of the device queue limits. Avoid such deadlock by not freezing the queue before calling the -&gt;store_limit() method in struct queue_sysfs_entry and instead use the queue_limits_commit_update_frozen helper to freeze the queue after taking the limits lock. This also removes taking the sysfs lock for the store_limit method as it doesn&#39;t protect anything here, but creates even more nesting. Hopefully it will go away from the actual sysfs methods entirely soon. (commit log adapted from a similar patch from Damien Le Moal)</p> <p><strong>Affected:</strong> 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 75 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: block: fix queue freeze vs limits lock order in sysfs store methods queue_attr_store() always freezes a device queue before calling the attribute store operation. For attributes that control queue limits, the store operation will also lock the queue limits with a call to queue_limits_start_update(). However, some drivers (e.g. SCSI sd) may need to issue commands to a device to obtain limit values from the hardware with the queue limits locked. This creates a potential ABBA deadlock situation if a user attempts to modify a limit (thus freezing the device queue) while the device driver starts a revalidation of the device queue limits. Avoid such deadlock by not freezing the queue before calling the -&gt;store_limit() method in struct queue_sysfs_entry and instead use the queue_limits_commit_update_frozen helper to freeze the queue after taking the limits lock. This also removes taking the sysfs lock for the store_limit method as it doesn&#39;t protect anything here, but creates even more nesting. Hopefully it will go away from the actual sysfs methods entirely soon. (commit log adapted from a similar patch from Damien Le Moal)</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-21807 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0461 <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher spezifizierte Auswirkungen zu erzielen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher spezifizierte Auswirkungen zu erzielen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0461