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-99062vsock/virtio: account only unread bytes in read_skb()

Description

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: account only unread bytes in read_skb() After a partial stream receive, rx_bytes tracks the unread suffix while buf_used and peer credit still cover the whole packet. virtio_transport_read_skb() dequeues that packet but passes pkt_len for both counters, underflowing rx_bytes. On a connected CID_LOCAL stream with an SK_SKB verdict, a 40-byte read from a 100-byte packet made SIOCINQ report -40, an empty recv return ELOOP, and poll report the empty socket readable. After verdict detach, receiving 40 bytes wrapped the counter to zero and hid those queued bytes until one more byte arrived. The fixed run kept the counter balanced and exposed all queued data immediately. This was found during an LLM-assisted manual source audit of VSOCK receive accounting while re-evaluating virtio_transport_read_skb() after CVE-2024-50169. Subtract only skb->len minus the VSOCK offset from rx_bytes. Retain the full packet length for buf_used and peer credit.

Timeline

  1. ID reserved

    By Linux

  2. · 28 days later

    Published

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7893a41deaf28b53036d4ea7cd9f7d54e8874dfc – < e4a0028b0d54b2c45e1dc8c0dd95fe3e9236f55b
    • affected 45ca7e9f0730ae36fc610e675b990e9cc9ca0714 – < 38bad3930b1185dd6c98db3dd342ddc123c6f3ef
    • affected 45ca7e9f0730ae36fc610e675b990e9cc9ca0714 – < dd4b2f88ee517f9629d0d3dbfced02ffbc33e2dc
    • affected 45ca7e9f0730ae36fc610e675b990e9cc9ca0714 – < a463f55c791b96cfd12df8b10ea737d45c80bb18
    • affected 17bada47e9ac3621c28e0ffa89af8279fedea00a
    • affected 6.12.34 – < 6.12.113
    • affected 6.15.3 – < 6.16
  • Linux · Linux

    • affected 6.16
    • unaffected < 6.16
    • unaffected 6.12.113 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.11 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .