Linux kernel race condition crashes virtio_blk during device freeze
- Exploited
- No known exploitation
- Fix
- Fixed in 5.5, 5.11, 5.16, 6.2, 6.7, and 1 more
- Who is exposed
- Not reported
Summary
A race condition in the virtio_blk driver of the Linux kernel can cause a kernel crash during device freeze, because a dispatcher can use virtqueues that were already deleted or freed. The description does not say how an attacker would reach this flaw.
Written by a model
Original 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().
What to do
Upgrade to a fixed version: 5.5, 5.11, 5.16, 6.2, 6.7, or one of 1 more.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99682 (virtio_blk: use synchronous quiesce in virtblk_freeze_priv()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99682 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 5.4.289, fixed in 5.5; from 5.10.233, fixed in 5.11; from 5.15.176, fixed in 5.16; from 6.1.123, fixed in 6.2; from 6.6.69, fixed in 6.7; from 6.12.8, fixed in 6.13
- Linux Linux: versions 6.13
Fixed versions: 5.5, 5.11, 5.16, 6.2, 6.7, 6.13.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99682 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99682 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/55cc03a17478e7da75df133a4d94ffa47856fee6
- https://git.kernel.org/stable/c/76f6e24c08a613361fb636d492934cda705d8890
- https://git.kernel.org/stable/c/6c6dec7883f8eb10b326bc9d109a4990c885d949
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99682
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99682"}.Affected versions
- Linux LinuxFrom 5.4.289 · fixed in 5.5; From 5.10.233 · fixed in 5.11; From 5.15.176 · fixed in 5.16; From 6.1.123 · fixed in 6.2; From 6.6.69 · fixed in 6.7; From 6.12.8 · fixed in 6.13
- Linux Linux6.13
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99682 |
| Record | NVD · CVE-2026-99682 |
| Other links 3 | |
| Link | git.kernel.org · stable/c/55cc03a17478e7da75df133a4d94ffa47856fee6 |
| Link | git.kernel.org · stable/c/76f6e24c08a613361fb636d492934cda705d8890 |
| Link | git.kernel.org · stable/c/6c6dec7883f8eb10b326bc9d109a4990c885d949 |
Questions about CVE-2026-99682
Is CVE-2026-99682 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99682?
Linux: from 5.4.289 before 5.5; from 5.10.233 before 5.11; from 5.15.176 before 5.16; from 6.1.123 before 6.2; from 6.6.69 before 6.7; from 6.12.8 before 6.13. Linux: version 6.13.
Source: cve.now feed data
How do I fix CVE-2026-99682?
Upgrade to a fixed version: 5.5, 5.11, 5.16, 6.2, 6.7, or one of 1 more.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.