CVE-2026-99635: vhost/vsock: size receive SKBs from declared payload

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

vhost/vsock: size receive SKBs from declared payload

vhostvsockallocskb() sizes the skb from iovlength(), the total guest descriptor length. virtiotransportincrxpkt() instead adds hdr->len to rxbytes and bufused, and budgets each queued skb as SKBTRUESIZE(0). The guest controls the descriptor length and hdr->len independently.

A guest can therefore provide a 64 KiB descriptor while declaring a zero payload. The descriptor-sized skb remains queued, rxbytes and bufused remain unchanged, and only the fixed queue-entry budget limits retention. This is not a lifetime leak: the skb is freed when dequeued or at socket teardown. Repeating this across connections can nevertheless exhaust host memory. On Linux v7.2, 455 such descriptors retained 30,255,680 bytes for a 262,144-byte receive buffer; a full-payload control retained 265,984 bytes.

Vhost previously read hdr->len and allocated pkt->buf from that value. The conversion from virtiovsockpkt to skbuff instead allocated receive skbs from the descriptor length, introducing the allocation-accounting mismatch.

Copy the header into a stack object and validate hdr->len before allocating the skb. Size the allocation as sizeof(hdr) + payloadlen so descriptor capacity no longer determines queued memory. Check payloadlen against len - sizeof(hdr) to avoid addition overflow on 32-bit hosts.

Affected Software

4 affected componentsFixes available
linux/kernel>=6.1.63<6.2
6.2
linux/kernel>=6.3.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.2
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  4. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  5. Compensating control

    In vhost/vsock, copy the header into a stack object and validate hdr->len before allocating. Check payload_len against hdr->len - sizeof(hdr) to avoid addition overflow on 32-bit hosts, then size the receive skb allocation as sizeof(hdr) + payload_len rather than from the descriptor length.

Frequently Asked Questions

1

Who is exposed to this issue?

Hosts using the Linux kernel vhost/vsock implementation are exposed to a malicious or compromised guest that can supply virtio-vsock receive descriptors. The guest controls both the descriptor length and the declared payload length.

2

What does an attacker need to do to trigger the memory exhaustion?

The guest can provide a large descriptor, such as 64 KiB, while declaring a zero-length payload. The resulting descriptor-sized skb can remain queued without corresponding rx_bytes or buf_used accounting, and repetition across connections can exhaust host memory.

3

Does this create a permanent memory leak?

No. Queued skbs are freed when they are dequeued or when the socket is torn down. However, an attacker can retain substantial host memory while the skbs remain queued and repeat the condition across connections.

4

How can affected behavior be recognized?

A vulnerable host can show disproportionately high memory retained by queued vhost/vsock receive buffers despite little or no declared payload and unchanged receive-buffer accounting. The described test retained 30,255,680 bytes with 455 zero-payload 64 KiB descriptors for a 262,144-byte receive buffer.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203