CVE-2026-53132: Linux kernel · vsock/virtio: fix potential unbounded skb queue
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in 100d5b2ffdc6468b9e48532641f29e83efdcb63c : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in 100d5b2ffdc6468b9e48532641f29e83efdcb63c, 059b7dbd20a6f0c539a45ddff1573cb8946685b5, 9bdc637fde66b63d6cad0caacd034888bb7bf5f5 +2
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix potential unbounded skb queue virtio_transport_inc_rx_pkt() checks vvs->rx_bytes + len > vvs->buf_alloc. virtio_transport_recv_enqueue() skips coalescing for packets with VIRTIO_VSOCK_SEQ_EOM. If fed with packets with len == 0 and VIRTIO_VSOCK_SEQ_EOM, a very large number of packets can be queued because vvs->rx_bytes stays at 0. Fix this by estimating the skb metadata size: (Number of skbs in the queue) * SKB_TRUESIZE(0)
References
- git.kernel.org/stable/c/1eca304f97a34ed5e921e1f0e06c8b241f25bf12 (opens in a new tab)
- git.kernel.org/stable/c/9bdc637fde66b63d6cad0caacd034888bb7bf5f5 (opens in a new tab)
- git.kernel.org/stable/c/100d5b2ffdc6468b9e48532641f29e83efdcb63c (opens in a new tab)
- git.kernel.org/stable/c/059b7dbd20a6f0c539a45ddff1573cb8946685b5 (opens in a new tab)