# CVE-2026-74614: vsock/virtio: read virtqueues under worker locks

> A race condition in the Linux kernel vsock driver allows workers to access deleted virtqueues, potentially causing system crashes or denial of service.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-97226, BELL-CVE-2026-74614, DEBIAN-CVE-2026-74614, GHSA-m75m-8448-cc2j, UBUNTU-CVE-2026-74614

## What is CVE-2026-74614?

CVE-2026-74614 is a high-severity vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

vsock/virtio: read virtqueues under worker locks

Commit bd50c5dc182b ("vsock/virtio: add support for device
suspend/resume") made the *_run flags transition from false to true when
restore installs replacement virtqueues.  The RX, TX and event workers
read their virtqueue before locking and checking the corresponding flag,
so a worker delayed across freeze and restore can observe the replacement
queue's running state while retaining a pointer to the deleted queue.

Read each virtqueue under its mutex after checking the run flag, keeping
the pointer and state in the same queue generation.

## Which versions are affected by CVE-2026-74614?


## How do I fix CVE-2026-74614?

Apply the vendor's patch.

## Is CVE-2026-74614 being exploited?

There is no known exploitation of CVE-2026-74614 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74614 and fix it if it is affected.

What it is: CVE-2026-74614 is a high-severity vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74614 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74614/ (Markdown: https://insights.sbomify.com/CVE-2026-74614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74614
- OSV: https://osv.dev/vulnerability/CVE-2026-74614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74614/
Summaries are generated and may contain mistakes; the official description above is the record.