Skip to main content
VulnerabilityPublished

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d5e912448cd98b261eba8e35ab838f2dc69a79f5 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 06:04 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d5e912448cd98b261eba8e35ab838f2dc69a79f5, 9819add3aeb66dc823db0a82337f55481ad463be, 92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.1.63 <6.2
Fixed in
  • d5e912448cd98b261eba8e35ab838f2dc69a79f5
  • 9819add3aeb66dc823db0a82337f55481ad463be
  • 92ac18f7de67c7cb35b71e9872b08fb9ba9a6bf8
  • 89a2f2251a06751ddabbd6a39c207236b8bd42d5
  • 6.2
LinuxLinuxAffected
  • =6.3
Fixed in–

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.

References

Community reviews

Loading reviews…