CVE-2025-21807 Details
Description
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 ->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'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)
A deadlock vulnerability has been identified in the Linux kernel's handling of device queue limits. When a user modifies a queue limit, the device queue is frozen, potentially leading to a deadlock if the device driver simultaneously revalidates the queue limits. This issue arises because some drivers, like SCSI sd, must communicate with the hardware to retrieve limit values, creating an ABBA deadlock scenario. The vulnerability has been addressed by changing the order of operations when updating queue limits, ensuring that the queue is only frozen after the limits have been safely updated, thus preventing the deadlock situation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1645cd7fd42c236c952e9228badcac4fea1829ea | kernel.org | |
| https://git.kernel.org/stable/c/8985da5481562e96b95e94ed8e5cc9b6565eb82b | kernel.org | Patch |
| https://git.kernel.org/stable/c/c99f66e4084a62a2cc401c4704a84328aeddc9ec | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.9, < 6.13.2 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 18, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 28, 2025 | Initial Analysis | [email protected] |
| Feb 27, 2025 | New CVE Received | kernel.org |