Skip to main content
VulnerabilityPublished

CVE-2026-99682: Linux kernel · virtio_blk: use synchronous quiesce in virtblk_freeze_priv()

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99682· High

Not known to be exploited · fixed in 76f6e24c08a613361fb636d492934cda705d8890 : patch Linux kernel soon.

Data as of 20 Nov 2026, 07:34 UTC

Severity
High

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 76f6e24c08a613361fb636d492934cda705d8890, 55cc03a17478e7da75df133a4d94ffa47856fee6, 6c6dec7883f8eb10b326bc9d109a4990c885d949 +6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.4.289 <5.5
  • >=5.10.233 <5.11
  • >=5.15.176 <5.16
  • >=6.1.123 <6.2
  • >=6.6.69 <6.7
  • >=6.12.8 <6.13
Fixed in
  • 76f6e24c08a613361fb636d492934cda705d8890
  • 55cc03a17478e7da75df133a4d94ffa47856fee6
  • 6c6dec7883f8eb10b326bc9d109a4990c885d949
  • 6.13
  • 6.7
  • 6.2
  • 5.16
  • 5.11
  • 5.5
LinuxLinuxAffected
  • =6.13
Fixed in–

Description

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().

References

Community reviews

Loading reviews…