virtio-blk: don't keep queue frozen during system suspend
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9e323f856cf4963120e0e3892a84ef8bd764a0e4, Kernel 5.15.176, Kernel 5.4.289 and 12 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=db48acce75d73dfe51c43d56893cce067b73cf08 <9e323f856cf4963120e0e3892a84ef8bd764a0e4, >=5.15.150 <5.15.176, >=5.4.270 <5.4.289, >=5fe446b245ba61ddc924d7db280bcd987c39357a <9ca428c6397abaa8c38f5c69133a2299e1efbbf2, >=6.1.80 <6.1.123, >=6.6.19 <6.6.69, >=6.7.7 <6.8, >=8946924ff324853df6b7c525a7467d964dfd11c3 <12c0ddd6c551c1e438b087f874b4f1223a75f7ea, >=b7bfaea8f5ecd290864f5ae4c69859b89832b4dc <d738f3215bb4f88911ff4579780a44960c8e0ca5, =2b5128c714d863cd8d259aa9d87bed2d6aa6a5a8, =6.8, =c67ed40b1b4a66e3a13b21bdfbd0151639da5240, >=2a52590ac52394540351d8289cc2af0b83cf7d31 <6dea8e3de59928974bf157dd0499d3958d744ae4, >=4.19.308 <4.20, >=4ce6e2db00de8103a0687fb0f65fd17124a51aaa <7678abee0867e6b7fb89aa40f6e9f575f755fb37, >=4ce6e2db00de8103a0687fb0f65fd17124a51aaa <92d5139b91147ab372a17daf5dc27a5b9278e516, >=5.10.211 <5.10.233 | 9e323f856cf4963120e0e3892a84ef8bd764a0e4, 5.15.176, 5.4.289, 9ca428c6397abaa8c38f5c69133a2299e1efbbf2, 6.1.123, 6.6.69, 6.8, 12c0ddd6c551c1e438b087f874b4f1223a75f7ea, d738f3215bb4f88911ff4579780a44960c8e0ca5, 6dea8e3de59928974bf157dd0499d3958d744ae4, 4.20, 7678abee0867e6b7fb89aa40f6e9f575f755fb37, 92d5139b91147ab372a17daf5dc27a5b9278e516, 5.10.233 |
| linux-kernel: Kernel | >=5.10.211 <5.10.233, >=5.15.150 <5.15.176, >=5.4.270 <5.4.289, >=6.1.80 <6.1.123, >=6.6.19 <6.6.69, >=6.7.7 <6.8, >=6.8.0 <6.12.8, >=4.19.308 <4.20 | 5.10.233, 5.15.176, 5.4.289, 6.1.123, 6.6.69, 6.8, 6.12.8, 4.20 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket