CVE-2026-99682
What it is
In the Linux kernel, the following vulnerability has been resolved: virtio_blk: use synchronous quiesce in virtblk_freeze_priv() blk_mq_run_work_fn() can call blk_mq_sched_dispatch_requests() through blk_mq_run_dispatch_ops(). The dispatcher checks QUEUE_FLAG_QUIESCED while the flag is clear. It can then be preempted before it gets a request. At that time, it has no queue usage reference, so blk_mq_freeze_queue() does not wait for it. virtblk_freeze_priv() then calls blk_mq_quiesce_queue_nowait() and blk_mq_unfreeze_queue(). A new request can enter the queue. The old dispatcher can run again, use its old flag check, get the new request, and call virtio_queue_rq(). At the same time, virtblk_freeze_priv() can reset the device, delete the virtqueues, and free vblk->vqs. The old dispatcher can then use a deleted virtqueue or a NULL vblk->vqs, and the kernel can crash. Fix this by using blk_mq_quiesce_queue(), which waits for dispatch code that was already running. Keep the existing freeze and unfreeze order. The queue remains quiesced until virtblk_restore_priv() calls blk_mq_unquiesce_queue().
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < 55cc03a17478e7da75df133a4d94ffa47856fee6
- Linux < 76f6e24c08a613361fb636d492934cda705d8890
- Linux < 6c6dec7883f8eb10b326bc9d109a4990c885d949
- Linux d738f3215bb4f88911ff4579780a44960c8e0ca5
- Linux 9ca428c6397abaa8c38f5c69133a2299e1efbbf2
- Linux 6dea8e3de59928974bf157dd0499d3958d744ae4
- Linux 9e323f856cf4963120e0e3892a84ef8bd764a0e4
- Linux 12c0ddd6c551c1e438b087f874b4f1223a75f7ea
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99682.md and follow it. Check whether this project is affected by CVE-2026-99682. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.