CVE-2026-99123: vsock/virtio: validate packet source for connected sockets
In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: validate packet source for connected sockets
virtiotransportrecvpkt() looks up sockets first by the full source and destination tuple, then by destination only in the bound table. The fallback is needed for listening and connecting sockets, but sockets remain in the bound table after connect(), so it can also return a non-listening socket.
The fallback does not validate the source address. In TCPSYNSENT, a RESPONSE from an unrelated source can transition the victim socket to TCPESTABLISHED while its stored remote address remains unchanged. Subsequent RW packets from that source are delivered through the same destination-only fallback.
This was reproduced with capability-empty processes under different UIDs. The attacker discovered the target tuple through unprivileged AFVSOCK sockdiag and caused the victim socket to read 16 attacker-chosen bytes; the intended peer-side socket read 0 of those 16 bytes.
Add vsockchecksource() to validate the transport, source port and source CID against the peer stored in a non-listening socket. The local transport is the CID exception because its packets are generated internally with VMADDRCIDLOCAL as their source, including connections using CID aliases.
Use the helper after locksock() in the virtio receive path.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.15.224 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.161 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.115 - 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
azurelinux/kernelto a version that resolves this vulnerability.Fixed in 6.6.161.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.192-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.13-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.115-2~deb12u1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.192-2Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.117-1~deb12u1 - Compensating control
In the Linux kernel virtio receive path, call vsock_check_source() after lock_sock() to validate the transport, source port, and source CID against the peer stored in a non-listening socket; allow VMADDR_CID_LOCAL as the source-CID exception for the local transport.
Event History
Frequently Asked Questions
Which systems and applications are exposed?
Systems using connected AF_VSOCK sockets over the virtio transport are affected by the described behavior. The issue concerns non-listening sockets that remain in the bound table after connect().
What does an attacker need to exploit this?
An attacker can be a capability-empty process running under a different UID. In the reported reproduction, the attacker used unprivileged AF_VSOCK sock_diag to discover the target tuple, then sent a RESPONSE and subsequent RW packets from an unrelated source.
Does separating processes by UID or removing capabilities prevent exploitation?
No. The vulnerability was reproduced between capability-empty processes running under different UIDs.
What is the demonstrated impact?
An unrelated source can cause a socket in TCP_SYN_SENT to enter TCP_ESTABLISHED and have its packets delivered to the victim. The reproduction caused the victim to read 16 attacker-chosen bytes while the intended peer read none of those bytes.