vduse: Fix race in vduse_dev_msg_sync and vduse_dev_read_iter
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c8a6153b6c59d95c0e091f053f6f180952ade91e · < 8062ff9d366c4bc4ae775e14eac9a769f20c60dd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vduse: Fix race in vduse_dev_msg_sync and vduse_dev_read_iter
There is one race case in vduse_dev_msg_sync and vduse_dev_read_iter:
vduse_dev_read_iter(): lock(msg_lock); dequeue_msg(send_list); unlock(msg_lock); vduse_dev_msg_sync(): wait_timeout() finish lock(msg_lock); check msg->complete is false list_del(msg); <- double list_del() crash!
To fix this case, we shall ensure vduse_msg is on send_list or recv_list outside the msg_lock critical section.
From the CVE record · Linux
A race between vduse_dev_msg_sync and vduse_dev_read_iter can cause a double list deletion and crash the Linux kernel. It occurs when a message read overlaps a timed-out synchronous message operation; the input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel with vduse should check their kernel versions; affected versions are not specified.