CVE-2026-53132

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (4)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

vsock/virtio: fix potential unbounded skb queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9bdc637fde66b63d6cad0caacd034888bb7bf5f5
generic

vsock/virtio: fix potential unbounded skb queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1eca304f97a34ed5e921e1f0e06c8b241f25bf12
generic

vsock/virtio: fix potential unbounded skb queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/100d5b2ffdc6468b9e48532641f29e83efdcb63c
generic

vsock/virtio: fix potential unbounded skb queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/059b7dbd20a6f0c539a45ddff1573cb8946685b5

Vendor Advisories for CVE-2026-53132(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 78× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 04:21 UTCGHSA enrichment
  2. 2026-07-26 15:15 UTCEG score recompute
  3. 2026-07-26 15:14 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-25 14:18 UTCEPSS rescore
  6. 2026-07-24 14:18 UTCEPSS rescore
  7. 2026-07-23 14:18 UTCEPSS rescore
  8. 2026-07-23 03:19 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:25 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-17 05:14 UTCGHSA enrichment
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 16:11 UTCGHSA enrichment
  18. 2026-07-16 03:11 UTCGHSA enrichment
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 14:12 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-15 01:13 UTCGHSA enrichment
  25. 2026-07-14 12:15 UTCGHSA enrichment
Show 57 more
  1. 2026-07-13 23:16 UTCGHSA enrichment
  2. 2026-07-13 22:31 UTCEPSS rescore
  3. 2026-07-13 10:18 UTCGHSA enrichment
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 21:18 UTCGHSA enrichment
  7. 2026-07-12 07:40 UTCGHSA enrichment
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-11 18:41 UTCGHSA enrichment
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 05:42 UTCGHSA enrichment
  13. 2026-07-10 16:44 UTCGHSA enrichment
  14. 2026-07-10 03:46 UTCGHSA enrichment
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-09 14:42 UTCGHSA enrichment
  18. 2026-07-09 01:29 UTCGHSA enrichment
  19. 2026-07-08 15:16 UTCEPSS rescore
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-08 12:24 UTCGHSA enrichment
  22. 2026-07-07 23:20 UTCGHSA enrichment
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-07 10:21 UTCGHSA enrichment
  26. 2026-07-06 21:10 UTCGHSA enrichment
  27. 2026-07-06 16:27 UTCEPSS rescore
  28. 2026-07-06 16:27 UTCEPSS rescore
  29. 2026-07-06 08:06 UTCGHSA enrichment
  30. 2026-07-05 19:08 UTCGHSA enrichment
  31. 2026-07-05 06:09 UTCGHSA enrichment
  32. 2026-07-05 02:31 UTCEPSS rescore
  33. 2026-07-05 02:30 UTCEPSS rescore
  34. 2026-07-04 17:09 UTCGHSA enrichment
  35. 2026-07-04 06:31 UTCEPSS rescore
  36. 2026-07-04 06:31 UTCEPSS rescore
  37. 2026-07-04 04:09 UTCGHSA enrichment
  38. 2026-07-03 14:45 UTCGHSA enrichment
  39. 2026-07-03 01:47 UTCGHSA enrichment
  40. 2026-07-02 12:48 UTCGHSA enrichment
  41. 2026-07-01 23:50 UTCGHSA enrichment
  42. 2026-07-01 15:07 UTCEPSS rescore
  43. 2026-07-01 10:52 UTCGHSA enrichment
  44. 2026-06-30 23:22 UTCEPSS rescore
  45. 2026-06-30 21:52 UTCEG score recompute 7.10
  46. 2026-06-30 21:52 UTCGHSA enrichment
  47. 2026-06-29 14:06 UTCEPSS rescore
  48. 2026-06-29 14:06 UTCEPSS rescore
  49. 2026-06-28 14:07 UTCEPSS rescore
  50. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  51. 2026-06-28 04:56 UTCEPSS rescore
  52. 2026-06-28 04:56 UTCEPSS rescore
  53. 2026-06-28 04:01 UTCGHSA enrichment
  54. 2026-06-27 03:08 UTCEPSS rescore
  55. 2026-06-25 13:49 UTCEPSS rescore
  56. 2026-06-25 10:10 UTCEG score recompute
  57. 2026-06-25 10:10 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53132?
CVE-2026-53132 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix potential unbounded skb queue virtiotransportincrxpkt() checks vvs->rxbytes + len > vvs->bufalloc. virtiotransportrecv_enqueue() skips coalescing for packets with VIRTIOVSOCKSEQ_EOM. If fed with packets with len…
When was CVE-2026-53132 disclosed?
CVE-2026-53132 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53132 actively exploited?
CVE-2026-53132 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53132?
CVE-2026-53132 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-53132?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53132, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53132

Explore →

Is Your Infrastructure Affected by CVE-2026-53132?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.