UNKNOWN NVD
CVE-2026-74614
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: read virtqueues under worker locks Commit bd50c5dc182b ("vsock/virtio: add s
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.
References
- https://git.kernel.org/stable/c/1cecb4202afdbeddcf29d59baf596ac6ab753f7f
- https://git.kernel.org/stable/c/29dd10583bf9d2744cd84b862e4257c0a5699570
- https://git.kernel.org/stable/c/941329ce14c5f481223a10d1d4c8b57ea7f3048a
- https://git.kernel.org/stable/c/a1fb0c5b8a7c2753758aeced40971f99449dde0c
- https://git.kernel.org/stable/c/bd43a7ec668be428265b3209eb43647aedcf720a
This unknown severity vulnerability was published on 2026-08-22 via NVD.
vulnfeed aggregates 11022 vulnerabilities from NVD, CISA KEV,
Ubuntu, Debian, Red Hat, Kubernetes, Exploit-DB, OSS-Security, GitHub and OpenStack — updated every 4 hours.