vsock/virtio: validate packet source for connected sockets
Summary
| CVE | CVE-2026-99123 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-28 11:17:31 UTC |
| Updated | 2026-10-28 11:17:31 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
vsock/virtio: validate packet source for connected sockets
virtio_transport_recv_pkt() 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 TCP_SYN_SENT, a
RESPONSE from an unrelated source can transition the victim socket to
TCP_ESTABLISHED 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 AF_VSOCK
sock_diag and caused the victim socket to read 16 attacker-chosen bytes;
the intended peer-side socket read 0 of those 16 bytes.
Add vsock_check_source() 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
VMADDR_CID_LOCAL as their source, including connections using CID aliases.
Use the helper after lock_sock() in the virtio receive path. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 06a8fc78367d070720af960dcecec917d3ae5f3b 6cd829de69efd9ed3a53aa2421004a0396eb2bd7 git |
Not specified |
| CNA |
Linux |
Linux |
affected 06a8fc78367d070720af960dcecec917d3ae5f3b e9bf92de436ba55f33eaa55d7008e68551123cfd git |
Not specified |
| CNA |
Linux |
Linux |
affected 06a8fc78367d070720af960dcecec917d3ae5f3b dee44f41f206becb41c492899c1996cfd7f82a1b git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.8 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.8 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.59 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.13 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/dee44f41f206becb41c492899c1996cfd7f82a1b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e9bf92de436ba55f33eaa55d7008e68551123cfd |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6cd829de69efd9ed3a53aa2421004a0396eb2bd7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.