vsock: remove vsock from connected table when connect is interrupted by a signal
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d021c344051af91f42c5ba9fdedc176740cbd238 · < 787468ee7a435777521d33399d012fd591ae2f94| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vsock: remove vsock from connected table when connect is interrupted by a signal
vsock_connect() expects that the socket could already be in the TCP_ESTABLISHED state when the connecting task wakes up with a signal pending. If this happens the socket will be in the connected table, and it is not removed when the socket state is reset. In this situation it's common for the process to retry connect(), and if the connection is successful the socket will be added to the connected table a second time, corrupting the list.
Prevent this by calling vsock_remove_connected() if a signal is received while waiting for a connection. This is harmless if the socket is not in the connected table, and if it is in the table then removing it will prevent list corruption from a double add.
Note for backporting: this patch requires d5afa82c977e ("vsock: correct removal of socket from the list"), which is in all current stable trees except 4.9.y.
From the CVE record · Linux
The Linux kernel’s vsock connection handling can leave a socket in the connected table when a signal interrupts connect(). If a local process retries and the connection succeeds, the socket can be added twice, corrupting the list; no authentication or other user interaction is specified.
Teams running Linux kernels with the affected vsock code should check their kernel vendor’s advisory for affected versions.