Skip to content
Threat Brief

← All advisories

CVE-2026-99635

Severity unknownNo known exploitationFix available

vhost/vsock: size receive SKBs from declared payload

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 6.1.63 before 6.26.2CVE Program
LinuxLinuxfrom 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 before 89a2f2251a06751ddabbd6a39c207236b8bd42d589a2f2251a06751ddabbd6a39c207236b8bd42d5CVE Program
LinuxLinuxfrom 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 before 9819add3aeb66dc823db0a82337f55481ad463be9819add3aeb66dc823db0a82337f55481ad463beCVE Program
LinuxLinuxfrom 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 before d5e912448cd98b261eba8e35ab838f2dc69a79f5d5e912448cd98b261eba8e35ab838f2dc69a79f5CVE Program
LinuxLinuxfrom 71dc9ec9ac7d3eee785cdc986c3daeb821381e20 before 92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf892ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8CVE Program
LinuxLinux6.3Not documentedCVE Program
LinuxLinuxbaddcc2c71572968cdaeee1c4ab3dc0ad90fa765Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.3Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references