vsock/vmci: fix sk_ack_backlog leak on failed handshake
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d021c344051af91f42c5ba9fdedc176740cbd238 · < ba9ad6015937a5e46ba1a31370e3efdec8abbdcc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vsock/vmci: fix sk_ack_backlog leak on failed handshake
When vmci_transport_recv_connecting_server() returns an error, vmci_transport_recv_listen() calls vsock_remove_pending() but never calls sk_acceptq_removed(). This leaves sk_ack_backlog incremented permanently.
Repeated handshake failures (malformed packets, queue pair alloc failure, event subscribe failure) cause sk_ack_backlog to climb toward sk_max_ack_backlog. Once it reaches the limit the listener permanently refuses all new connections with -ECONNREFUSED, a silent denial of service requiring a process restart to recover.
The two existing sk_acceptq_removed() calls in af_vsock.c do not cover this path: line 764 checks vsock_is_pending() which returns false after vsock_remove_pending(), and line 1889 is only reached on successful accept().
Fix by balancing sk_acceptq_added() with sk_acceptq_removed() on the error path.
From the CVE record · Linux
The Linux kernel’s vsock/vmci listener fails to decrement its connection backlog after a handshake error. Repeated failed handshakes can fill the backlog, causing the listener to refuse new connections until its process restarts. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with vsock/vmci should check for this issue; affected versions are not specified.