CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's virtio vsock implementation, where worker threads can read virtqueues without proper locking, potentially leading to inconsistent state observations during device suspend and resume operations. This flaw could allow an attacker to exploit the race condition, potentially leading to system instability or denial of service. Organizations using Linux in environments that leverage virtio for virtualized networking should prioritize patching this vulnerability to ensure system integrity and reliability.
Original NVD 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.