First published: Tue Jan 21 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-57946 has not been assigned a CVSS score, but it showcases a critical oversight in queue management during system suspend in the Linux kernel.
To remediate CVE-2024-57946, update your Linux kernel to the latest patch version that addresses this vulnerability.
CVE-2024-57946 affects specific versions of the Linux kernel that implement virtio-blk functionality, particularly prior to the fix release.
CVE-2024-57946 could potentially lead to data loss or corruption during system suspension due to improper handling of queued requests.
As a workaround for CVE-2024-57946, consider avoiding system suspensions until a patch can be applied.