vhost/vsock: size receive SKBs from declared payload
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d5e912448cd98b261eba8e35ab838f2dc69a79f5, Kernel 6.2, Kernel 89a2f2251a06751ddabbd6a39c207236b8bd42d5 and 5 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <d5e912448cd98b261eba8e35ab838f2dc69a79f5, >=6.1.63 <6.2, >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <89a2f2251a06751ddabbd6a39c207236b8bd42d5, >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8, >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <9819add3aeb66dc823db0a82337f55481ad463be, =6.3, =baddcc2c71572968cdaeee1c4ab3dc0ad90fa765 | d5e912448cd98b261eba8e35ab838f2dc69a79f5, 6.2, 89a2f2251a06751ddabbd6a39c207236b8bd42d5, 92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8, 9819add3aeb66dc823db0a82337f55481ad463be |
| linux-kernel: Kernel | >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=6.3.0 <6.12.118, >=6.1.63 <6.2 | 6.18.64, 7.3.5, 6.12.118, 6.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket