CVE-2025-21807: block: fix queue freeze vs limits lock order in sysfs store methods

Published Feb 27, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

block: fix queue freeze vs limits lock order in sysfs store methods

queueattrstore() 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 queuelimitsstartupdate(). 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 ->storelimit() method in struct queuesysfsentry and instead use the queuelimitscommitupdatefrozen helper to freeze the queue after taking the limits lock.

This also removes taking the sysfs lock for the storelimit 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)

Affected Software

4 affected componentsFixes available
Linux Kernel
Linux Linux kernel>=6.9<6.13.2
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1
debian/linux-6.12
6.12.113-1~deb12u1

Event History

Feb 27, 2025
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
Data Sourced
via NVD·08:16 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2025-21807?

CVE-2025-21807 has a medium severity rating due to potential impacts on device queue management.

2

How do I fix CVE-2025-21807?

To fix CVE-2025-21807, update to the latest stable version of the Linux kernel that includes the patch.

3

Who is affected by CVE-2025-21807?

CVE-2025-21807 affects systems running specific versions of the Linux kernel that utilize queue attribute manipulation.

4

What are the potential consequences of CVE-2025-21807?

Potential consequences of CVE-2025-21807 include race conditions that could lead to system instability during device queue operations.

5

Is there a workaround for CVE-2025-21807?

There are no formal workarounds for CVE-2025-21807; updating the kernel is the recommended approach.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203