CVE-2025-21807
Last modified
CVE-2025-21807 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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(). EPSS estimates a 0.12% chance of exploitation in the next 30 days.
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)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.9, < 6.13.2 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-21807?
How severe is CVE-2025-21807?
How do I fix CVE-2025-21807?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-21801In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21802In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21803In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21804In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21805In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21806In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21808In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21809In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-2181A sensitive information disclosure vulnerability in Palo Alt…5.9
- CVE-2025-21810In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21811In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21812In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-21807?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
