vsock/virtio: read virtqueues under worker locks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bd50c5dc182b0a52599f87b429f9a5a9cbfc9b1c · < 1cecb4202afdbeddcf29d59baf596ac6ab753f7f| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Linux kernel vsock/virtio workers can retain a pointer to a deleted virtqueue if they are delayed across device freeze and restore. They may then read the replacement queue’s running state while using the stale pointer. The input does not establish an attacker path or specify access, authentication, or user-interaction requirements.
Engineers running Linux kernels with vsock/virtio should check their versions; affected versions are not specified.