CVE-2026-53132
vsock/virtio: fix potential unbounded skb queue
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)
INFO
Published Date :
June 25, 2026, 9:16 a.m.
Last Modified :
July 6, 2026, 3:23 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Solution
- Update the Linux kernel to the latest version.
- Apply the specific patch for vsock/virtio.
- Restart affected services or systems.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53132.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53132 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53132
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53132 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53132 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 06, 2026
Action Type Old Value New Value Added CWE CWE-401 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.3:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.3:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.3:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.3:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.3:-:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.3:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.1.63 up to (excluding) 6.2 *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.36 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.13 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.3.1 up to (excluding) 6.12.94 Added Reference Type kernel.org: https://git.kernel.org/stable/c/059b7dbd20a6f0c539a45ddff1573cb8946685b5 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/100d5b2ffdc6468b9e48532641f29e83efdcb63c Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/1eca304f97a34ed5e921e1f0e06c8b241f25bf12 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9bdc637fde66b63d6cad0caacd034888bb7bf5f5 Types: Patch -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 28, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '077706165717686a2a6a71405fef036cd5b37ae0', 'lessThan': '1eca304f97a34ed5e921e1f0e06c8b241f25bf12', 'versionType': 'git'}, {'status': 'affected', 'version': '077706165717686a2a6a71405fef036cd5b37ae0', 'lessThan': '9bdc637fde66b63d6cad0caacd034888bb7bf5f5', 'versionType': 'git'}, {'status': 'affected', 'version': '077706165717686a2a6a71405fef036cd5b37ae0', 'lessThan': '100d5b2ffdc6468b9e48532641f29e83efdcb63c', 'versionType': 'git'}, {'status': 'affected', 'version': '077706165717686a2a6a71405fef036cd5b37ae0', 'lessThan': '059b7dbd20a6f0c539a45ddff1573cb8946685b5', 'versionType': 'git'}, {'status': 'affected', 'version': '5852a2b573f7a3a29df46296e56aa3491e589cdf', 'versionType': 'git'}, {'status': 'affected', 'version': '6.1.63', 'lessThan': '6.2', 'versionType': 'semver'}], 'programFiles': ['net/vmw_vsock/virtio_transport_common.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.3'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.3', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.12.94', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.36', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.13', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/vmw_vsock/virtio_transport_common.c'], 'defaultStatus': 'affected'}] Added 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) Added Reference https://git.kernel.org/stable/c/059b7dbd20a6f0c539a45ddff1573cb8946685b5 Added Reference https://git.kernel.org/stable/c/100d5b2ffdc6468b9e48532641f29e83efdcb63c Added Reference https://git.kernel.org/stable/c/1eca304f97a34ed5e921e1f0e06c8b241f25bf12 Added Reference https://git.kernel.org/stable/c/9bdc637fde66b63d6cad0caacd034888bb7bf5f5