Live › vulnerability › CVE-2026-99062
Go to dashboardA bug in the Linux kernel's virtio vsock receive path subtracts the wrong byte count after a partial read, so the socket's pending-byte counter underflows. The sources describe wrong SIOCINQ values, false readable polls, and hidden queued data, with no sign of memory corruption or code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with virtio vsock and SK_SKB verdict programs on connected CID_LOCAL stream sockets are the ones described. The sources do not say which distributions or kernel versions are affected, and ordinary hosts without vsock sockets are unlikely to be exposed.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99062")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.