CVE-2026-99122vsock/vmci: validate packet source for connected sockets
- 7.3HighCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 33 days later
· 33 days later
Published
- 13 days later
· 13 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.
Affected products
- affected d021c344051af91f42c5ba9fdedc176740cbd238 – < cdd1f99eaa4d4db82d506eb50e724460671c7cac
- affected d021c344051af91f42c5ba9fdedc176740cbd238 – < c027f8b429dbb2157fc1b503df196e272d947c89
- affected d021c344051af91f42c5ba9fdedc176740cbd238 – < 90c423b62ec9be08177f74b07a47937ca8d2035b
- affected d021c344051af91f42c5ba9fdedc176740cbd238 – < ad9a7da3fa39c2d616ec0dd3cf6e30531d032fe7
- affected 3.9
- unaffected < 3.9
- unaffected 6.12.117 – ≤ 6.12.*
- unaffected 6.18.59 – ≤ 6.18.*
- unaffected 7.2.13 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/cdd1f99eaa4d4db82d506eb50e724460671c7cac (opens in a new tab)
- https://git.kernel.org/stable/c/c027f8b429dbb2157fc1b503df196e272d947c89 (opens in a new tab)
- https://git.kernel.org/stable/c/90c423b62ec9be08177f74b07a47937ca8d2035b (opens in a new tab)
- https://git.kernel.org/stable/c/ad9a7da3fa39c2d616ec0dd3cf6e30531d032fe7 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-111874 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-99122)Record last updated .