CVE-2026-99122

vsock/vmci: validate packet source for connected sockets

Published Oct 28, 2026 CVSS 3.1 · 7.3 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

vsock/vmci: validate packet source for connected sockets

vmci_transport_recv_stream_cb() 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 TCP_SYN_SENT 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
vsock_check_source() after taking the socket lock in the bottom-half path,
and recheck after lock_sock() 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.

Analysis

AI-generated

Technical impact

An attacker can send a forged VMCI packet from an arbitrary context, causing the Linux kernel's vmci_transport_recv_stream_cb() to reset a socket that it does not own. The original implementation first matches sockets by a full source‑destination tuple and, if that fails, falls back to a destination‑only lookup without verifying that the packet came from the socket's stored peer. This flaw allows a malicious packet to be matched to a non‑listening socket and trigger a reset, thereby disrupting or terminating connections on the host. The impact is a denial of service and unintended state changes in network communication within the affected system.

Affected Systems

The flaw exists in the Linux kernel's VMCI subsystem. Any kernel that includes VMCI support and handles connected sockets is vulnerable. The exact kernel versions are not specified in the report, so all releases prior to the patch commit (c027f8b4) should be considered at risk.

Risk and Exploitability

The vulnerability is rooted in improper input validation. The CVSS score of 7.3, the EPSS score is < 1%, and it is not listed in the CISA KEV catalog, indicating limited reported exploitation. The likely attack vector is a local attacker with the ability to craft and inject VMCI packets, such as a privileged user or a compromised virtual machine inside the same host. While the exploit requires specific VMCI context control, exploitation could lead to disruption of services through unauthorized socket resets. The overall risk is moderate but should not be ignored in environments relying on VMCI.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that includes the vmci source validation fix (e.g., the latest stable release incorporating commit c027f8b4).
  • Reboot or otherwise ensure the updated kernel is active so that all vmci interfaces use the corrected logic.
  • If a kernel update is not possible, disable the VMCI subsystem by removing the vmci module or setting the appropriate kernel parameter to prevent the vulnerable path from being exercised.

Generated by OpenCVE AI on October 31, 2026 at 15:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Metrics cvssV3_1

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

cvssV3_1

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

Type Values Removed Values Added
Weaknesses CWE-346
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate

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/vmci: validate packet source for connected sockets vmci_transport_recv_stream_cb() 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 TCP_SYN_SENT 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 vsock_check_source() after taking the socket lock in the bottom-half path, and recheck after lock_sock() 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.
Title vsock/vmci: 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

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Nov 10, 2026, 6:15 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Nov 10, 2026, 7:22 PM
Severity
Moderate
Public date
Oct 28, 2026, 10:34 AM