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.
References7
- git.kernel.org/stable/c/1cecb4202afdbeddcf29d59baf596ac6ab753f7f
- git.kernel.org/stable/c/29dd10583bf9d2744cd84b862e4257c0a5699570
- git.kernel.org/stable/c/941329ce14c5f481223a10d1d4c8b57ea7f3048a
- git.kernel.org/stable/c/a1fb0c5b8a7c2753758aeced40971f99449dde0c
- git.kernel.org/stable/c/bd43a7ec668be428265b3209eb43647aedcf720a
- git.kernel.org/stable/c/eae099c764c7ebdb842eb1f638913e310bdd6513
- git.kernel.org/stable/c/ebac8f6b1ef0e9278afe204b8692a7479988dace
Metrics
- CVSS 3.1
-
8.4
HIGH
Score source: CNA
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 4 · as of 9 November 2026
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.