Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99123vsock/virtio: validate packet source for connected sockets

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.

Timeline

  1. ID reserved

    By Linux

  2. · 33 days later

    Published

  3. · 3 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

CVSS scores of CVE-2026-99123, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVDNVD · Received3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 06a8fc78367d070720af960dcecec917d3ae5f3b – < bda841af86cdfe7fcf4a2f4db22e27f1b852b1ff
    • affected 06a8fc78367d070720af960dcecec917d3ae5f3b – < c0a3a786a5e8b5007d6a3c34721ab052399ab2ad
    • affected 06a8fc78367d070720af960dcecec917d3ae5f3b – < f77fb90edca5385d0eecbfd6d2c8ef60afff24a9
    • affected 06a8fc78367d070720af960dcecec917d3ae5f3b – < ec231dd3b14e541ba1c4f842a7d152fb61037333
    • affected 06a8fc78367d070720af960dcecec917d3ae5f3b – < 6cd829de69efd9ed3a53aa2421004a0396eb2bd7
    • affected 06a8fc78367d070720af960dcecec917d3ae5f3b – < e9bf92de436ba55f33eaa55d7008e68551123cfd
    • affected 06a8fc78367d070720af960dcecec917d3ae5f3b – < dee44f41f206becb41c492899c1996cfd7f82a1b
  • Linux · Linux

    • affected 4.8
    • unaffected < 4.8
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.59 – ≤ 6.18.*
    • unaffected 7.2.13 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99123 badge
[![CVE-2026-99123](https://cveledger.app/badge/CVE-2026-99123.svg)](https://cveledger.app/cve/CVE-2026-99123)

Record last updated .