vsock/virtio: discard packets if the transport changes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c0cfa2d8a788fcf45df5bf4070ab2474c88d543a · < 2cb7c756f605ec02ffe562fb26828e4bcc5fdfc1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: discard packets if the transport changes
If the socket has been de-assigned or assigned to another transport, we must discard any packets received because they are not expected and would cause issues when we access vsk->transport.
A possible scenario is described by Hyunwoo Kim in the attached link, where after a first connect() interrupted by a signal, and a second connect() failed, we can find `vsk->transport` at NULL, leading to a NULL pointer dereference.
From the CVE record · Linux
The Linux kernel’s vsock/virtio transport can process unexpected packets after a socket is de-assigned or assigned to another transport. A local user who triggers an interrupted first connect() followed by a failed second connect() could cause a NULL pointer dereference when the kernel accesses vsk->transport.
Engineers running Linux kernels with vsock/virtio should check their systems; affected versions were not specified.