CVE-2026-99122

vsock/vmci: validate packet source for connected sockets

  • High 7.3

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.

Key facts

Published
28 Oct 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.121% likely to be exploited in the next 30 days, higher than 1.983% of CVEs (scores for 16 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.3CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • d021c344051af91f42c5ba9fdedc176740cbd238 up to but excluding cdd1f99eaa4d4db82d506eb50e724460671c7cac (affected)
  • d021c344051af91f42c5ba9fdedc176740cbd238 up to but excluding c027f8b429dbb2157fc1b503df196e272d947c89 (affected)
  • d021c344051af91f42c5ba9fdedc176740cbd238 up to but excluding 90c423b62ec9be08177f74b07a47937ca8d2035b (affected)
  • d021c344051af91f42c5ba9fdedc176740cbd238 up to but excluding ad9a7da3fa39c2d616ec0dd3cf6e30531d032fe7 (affected)
LinuxLinux
  • Default status: affected
  • 3.9 (affected)
  • 0 up to but excluding 3.9 (unaffected)
  • 6.12.117 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 28 Oct 2026 Published

References