CVE-2026-99122: vsock/vmci: validate packet source for connected sockets
In the Linux kernel, the following vulnerability has been resolved:
vsock/vmci: validate packet source for connected sockets
vmcitransportrecvstreamcb() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback can select a non-listening socket without checking whether the packet came from its stored peer.
This was reproduced with two VMCI contexts. A RST from the context not stored in a TCPSYNSENT socket reset that socket after it was selected by the destination-only lookup.
VMCI can process notification packets in bottom-half context when the socket is not owned by user context, or defer packets to a workqueue. Use vsockchecksource() after taking the socket lock in the bottom-half path, and recheck after locksock() in the workqueue path. Listening sockets continue to accept packets from any source.
Reply with a RST addressed from the received packet before dropping a source that fails validation. This preserves the existing reset behavior for bound non-listening and concurrently closed sockets without directing the reset to a connected socket's stored peer.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.117 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.59 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.2.13 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.13-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1 - Upgrade
Upgrade
ubuntu/linux-gcp-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1018.20~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-44.44 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1018.19 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1018.20 - Upgrade
Upgrade
ubuntu/linux-gketo a version that resolves this vulnerability.Fixed in 7.0.0-1011.12 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1019.19 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1019.19 - Upgrade
Upgrade
ubuntu/linux-vmwareto a version that resolves this vulnerability.Fixed in 7.0.0-1007.7 - Compensating control
In Linux kernel vsock/vmci, call vsock_check_source() after taking the socket lock in the bottom-half path and recheck after lock_sock() in the workqueue path. For a source that fails validation, send a RST addressed to the received packet before dropping it; keep listening sockets accepting packets from any source.
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using the Linux VMCI vsock transport are affected. The issue requires VMCI communication involving multiple VMCI contexts; the described reproduction uses a packet from a context other than the peer stored for a connected socket.
What can an attacker do if they can send VMCI packets from another context?
A packet, including a RST, can be selected through the destination-only bound-socket lookup even when its source does not match the connected socket's stored peer. In the reported case, a RST from a different VMCI context reset a socket in TCP_SYN_SENT state.
Are listening sockets restricted to an established peer by this fix?
No. Listening sockets continue to accept packets from any source. Source validation is applied to connected sockets after the socket is locked.
What happens to packets whose source fails validation after the fix?
The packet is dropped and a RST is sent using the received packet's source address. This avoids directing the reset to the connected socket's stored peer.