CVE-2024-57946

virtio-blk: don't keep queue frozen during system suspend

MEDIUM
5.5
CVSS Score
Published: January 21, 2025 at 12:22 PM UTC
Updated: June 17, 2026 at 08:14 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: virtio-blk: don't keep queue frozen during system suspend Commit 4ce6e2db00de ("virtio-blk: Ensure no requests in virtqueues before deleting vqs.") replaces queue quiesce with queue freeze in virtio-blk's PM callbacks. And the motivation is to drain inflight IOs before suspending. block layer's queue freeze looks very handy, but it is also easy to cause deadlock, such as, any attempt to call into bio_queue_enter() may run into deadlock if the queue is frozen in current context. There are all kinds of ->suspend() called in suspend context, so keeping queue frozen in the whole suspend context isn't one good idea. And Marek reported lockdep warning[1] caused by virtio-blk's freeze queue in virtblk_freeze(). [1] https://lore.kernel.org/linux-block/[email protected]/ Given the motivation is to drain in-flight IOs, it can be done by calling freeze & unfreeze, meantime restore to previous behavior by keeping queue quiesced during suspend.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.19.308v ≥ 6.7.7v < 5.4.2894.19.308 ≤ v < 4.205.10.211 ≤ v < 5.10.2335.11 ≤ v < 5.15.1765.15.150 ≤ v < 5.15.1765.16 ≤ v < 6.1.1235.4.270 ≤ v < 5.4.2895.5 ≤ v < 5.10.2336.1.80 ≤ v < 6.1.1236.2 ≤ v < 6.6.696.6.19 ≤ v < 6.6.696.7 ≤ v < 6.12.86.7.7 ≤ v < 6.86.8 ≤ v < 6.12.86.8 ≤ v < 6.132a52590ac52394540351d8289cc2af0b83cf7d312b5128c714d863cd8d259aa9d87bed2d6aa6a5a84.19.3084ce6e2db00de8103a0687fb0f65fd17124a51aaa5.10.2115.15.1505.4.2705fe446b245ba61ddc924d7db280bcd987c39357a6.1.806.13 rc16.13 rc26.13 rc36.13 rc46.13 rc56.13 rc66.6.196.7.78946924ff324853df6b7c525a7467d964dfd11c3b7bfaea8f5ecd290864f5ae4c69859b89832b4dcc67ed40b1b4a66e3a13b21bdfbd0151639da5240db48acce75d73dfe51c43d56893cce067b73cf08
Vendor states this is fixed in 12c0ddd6c551c1e438b087f874b4f1223a75f7ea (fixed)
Vendor states this is fixed in 6dea8e3de59928974bf157dd0499d3958d744ae4 (fixed)
Vendor states this is fixed in 7678abee0867e6b7fb89aa40f6e9f575f755fb37 (fixed)
Vendor states this is fixed in 92d5139b91147ab372a17daf5dc27a5b9278e516 (fixed)
Vendor states this is fixed in 9ca428c6397abaa8c38f5c69133a2299e1efbbf2 (fixed)
Vendor states this is fixed in 9e323f856cf4963120e0e3892a84ef8bd764a0e4 (fixed)
Vendor states this is fixed in d738f3215bb4f88911ff4579780a44960c8e0ca5 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.233 (unaffected)
Vendor states this is fixed in 5.15.176 (unaffected)
Vendor states this is fixed in 5.4.289 (unaffected)
Vendor states this is fixed in 6.1.123 (unaffected)
Vendor states this is fixed in 6.12.8 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.6.69 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (9)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/12c0ddd6c551c1e438b087f874b4f1223a75f7ea
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6dea8e3de59928974bf157dd0499d3958d744ae4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7678abee0867e6b7fb89aa40f6e9f575f755fb37
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/92d5139b91147ab372a17daf5dc27a5b9278e516
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9ca428c6397abaa8c38f5c69133a2299e1efbbf2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9e323f856cf4963120e0e3892a84ef8bd764a0e4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d738f3215bb4f88911ff4579780a44960c8e0ca5
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card