CVE-2026-99123

vsock/virtio: validate packet source for connected sockets

Published Oct 28, 2026 CVSS 3.1 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Linux kernel’s virtio_transport_recv_pkt() function does not validate the source of packets for connected VSOCK sockets. If a socket is already in the established state, a packet that originates from an unrelated source can be matched by the fallback destination‑only lookup, causing the socket to transition to TCP_ESTABLISHED while the stored remote address remains unchanged. An attacker can then send arbitrary data that will be read by the victim process, enabling data injection or potential code execution. This flaw is an instance of improper source validation, represented by CWE‑940.

Affected Systems

Any Linux kernel build that incorporates virtio VSOCK networking and has not applied the commit adding vsock_check_source() is vulnerable. The flaw was fixed in later kernel releases, but no specific affected version range is provided in the CNA data. Therefore, all kernels using the virtio transport prior to the patch should be considered at risk.

Risk and Exploitability

The vulnerability has a CVSS score of 7.1 and an EPSS score of < 1%, and it is not listed in the CISA KEV catalog. However, the flaw allows an attacker with access to the VSOCK network to hijack a socket and inject arbitrary payloads, which could lead to remote code execution if the victim application processes data unsafely. Discovery of the target socket requires only unprivileged AF_VSOCK sock_diag calls and knowledge of the victim’s CID and port, conditions that are realistically obtainable within a virtualized environment. These factors, combined with the absence of a validation check, make the vulnerability high risk and should prompt prompt remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Deploy a kernel build that includes the vsock_check_source() patch (commit 6cd829de69…).
  • Reboot the system to ensure the patched kernel is active.
  • If using a vendor-supplied kernel, apply the vendor's security update or backport the patch, and configure the virtualization host to restrict VSOCK connections to trusted CID ranges.

Generated by OpenCVE AI on October 31, 2026 at 13:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
Debian DLA Debian DLA DLA-4906-1 linux security update
History
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 3.6, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L'}

cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Weaknesses CWE-940
References
Metrics threat_severity

None

cvssV3_1

{'score': 3.6, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L'}

threat_severity

Low

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
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.
Title vsock/virtio: validate packet source for connected sockets
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-940

    Improper Verification of Source of a Communication Channel

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 31, 2026, 12:43 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 31, 2026, 1:17 PM
Severity
Low
Public date
Oct 28, 2026, 10:34 AM