CVE-2026-99635

vhost/vsock: size receive SKBs from declared payload

State
Published
Severity
Not scored
Published
Nov 20, 2026
Updated
Nov 20, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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

vhost/vsock: size receive SKBs from declared payload

vhost_vsock_alloc_skb() sizes the skb from iov_length(), the total guest descriptor length. virtio_transport_inc_rx_pkt() instead adds hdr->len to rx_bytes and buf_used, and budgets each queued skb as SKB_TRUESIZE(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, rx_bytes and buf_used 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 virtio_vsock_pkt to sk_buff 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) + payload_len so descriptor capacity no longer determines queued memory. Check payload_len against len - sizeof(hdr) to avoid addition overflow on 32-bit hosts.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 to before 92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8Affected
  • 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 to before 89a2f2251a06751ddabbd6a39c207236b8bd42d5Affected
  • 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 to before 9819add3aeb66dc823db0a82337f55481ad463beAffected
  • 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 to before d5e912448cd98b261eba8e35ab838f2dc69a79f5Affected
  • baddcc2c71572968cdaeee1c4ab3dc0ad90fa765Affected
  • 6.1.63 to before 6.2Affected
LinuxLinux
  • 6.3Affected
  • before 6.3Not affected
  • 6.12.118 through 6.12.*Not affected
  • 6.18.64 through 6.18.*Not affected
  • 7.3.5 through 7.3.*Not affected
  • 7.4-rc2 and laterNot affected

References

Every record here comes from the CVE Program's CVE List. © 1999-2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.

© 2026 NVIDIA, the NVIDIA logo, and NVIDIA Inception are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries.