Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2024-57946

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.4.289, 5.10.233, 5.15.176, 6.1.123, 6.6.69, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

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/ca16370e-d646-4eee-b9cc-87277c89c43c@samsung.com/ 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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • Linux Linux

    From 5.4.270 · fixed in 5.4.289; From 5.10.211 · fixed in 5.10.233; From 5.15.150 · fixed in 5.15.176; From 6.1.80 · fixed in 6.1.123; From 6.6.19 · fixed in 6.6.69; From 4.19.308 · fixed in 4.20; From 6.7.7 · fixed in 6.8

  • Linux Linux

    6.8

References 7

git.kernel.org