CVE-2026-53181

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: 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/vmci: fix sk_ack_backlog leak on failed handshake

When vmci_transport_recv_connecting_server() returns an error, vmci_transport_recv_listen() calls vsock_remove_pending() but never calls sk_acceptq_removed(). This leaves sk_ack_backlog incremented permanently.

Repeated handshake failures (malformed packets, queue pair alloc failure, event subscribe failure) cause sk_ack_backlog to climb toward sk_max_ack_backlog. Once it reaches the limit the listener permanently refuses all new connections with -ECONNREFUSED, a silent denial of service requiring a process restart to recover.

The two existing sk_acceptq_removed() calls in af_vsock.c do not cover this path: line 764 checks vsock_is_pending() which returns false after vsock_remove_pending(), and line 1889 is only reached on successful accept().

Fix by balancing sk_acceptq_added() with sk_acceptq_removed() on the error path.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (8)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea0b03d52881c12a8c634ea0d6cbfa61cefdb488
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfd853197615d322d3a88dbcab91fc0fd2096219
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cf7090e255d74c4b61c51f8ede9fcacdd8393b5b
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c05fa14db43ebef3bd862ca9d073981c0358b3f0
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bcb275626055df7f8f947f1a349754b4004d9a15
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba9ad6015937a5e46ba1a31370e3efdec8abbdcc
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9698582a4dd9c4a05889d7db96d4c0edc9e69cac
generic

vsock/vmci: fix sk_ack_backlog leak on failed handshake - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22c587aa3ab1ab5264daff3ec32136fd30436c13

Vendor Advisories for CVE-2026-53181(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 / 73× 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-26 15:13 UTCEG score recompute
  2. 2026-07-26 15:13 UTCVendor advisory
  3. 2026-07-26 15:13 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-19 02:29 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 11:42 UTCGHSA enrichment
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 09:59 UTCVendor advisory
  21. 2026-07-15 09:59 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 08:18 UTCVendor advisory
  25. 2026-07-14 08:17 UTCGHSA enrichment
Show 52 more
  1. 2026-07-13 22:31 UTCEPSS rescore
  2. 2026-07-13 06:17 UTCVendor advisory
  3. 2026-07-13 06:16 UTCGHSA enrichment
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 04:29 UTCVendor advisory
  8. 2026-07-12 04:29 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-11 02:46 UTCVendor advisory
  12. 2026-07-11 02:46 UTCGHSA enrichment
  13. 2026-07-10 01:05 UTCVendor advisory
  14. 2026-07-10 01:05 UTCGHSA enrichment
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 19:10 UTCEPSS rescore
  17. 2026-07-08 23:21 UTCVendor advisory
  18. 2026-07-08 23:21 UTCGHSA enrichment
  19. 2026-07-08 15:16 UTCEPSS rescore
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-07 21:30 UTCVendor advisory
  22. 2026-07-07 21:30 UTCGHSA enrichment
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-07 13:46 UTCEPSS rescore
  25. 2026-07-06 19:48 UTCEG score recompute 5.50
  26. 2026-07-06 19:48 UTCVendor advisory
  27. 2026-07-06 19:47 UTCGHSA enrichment
  28. 2026-07-06 16:27 UTCEPSS rescore
  29. 2026-07-06 16:27 UTCEPSS rescore
  30. 2026-07-06 13:06 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-06 02:23 UTCEPSS rescore
  33. 2026-07-05 02:31 UTCEPSS rescore
  34. 2026-07-05 02:30 UTCEPSS rescore
  35. 2026-07-04 06:31 UTCEPSS rescore
  36. 2026-07-04 06:31 UTCEPSS rescore
  37. 2026-07-03 23:14 UTCVendor advisory
  38. 2026-07-03 23:13 UTCGHSA enrichment
  39. 2026-07-01 15:07 UTCEPSS rescore
  40. 2026-07-01 02:50 UTCVendor advisory
  41. 2026-07-01 02:50 UTCGHSA enrichment
  42. 2026-06-30 23:22 UTCEPSS rescore
  43. 2026-06-29 14:06 UTCEPSS rescore
  44. 2026-06-29 14:06 UTCEPSS rescore
  45. 2026-06-28 14:07 UTCEPSS rescore
  46. 2026-06-28 06:29 UTCGHSA enrichment
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-28 04:56 UTCEPSS rescore
  49. 2026-06-27 03:08 UTCEPSS rescore
  50. 2026-06-25 13:49 UTCEPSS rescore
  51. 2026-06-25 10:08 UTCEG score recompute
  52. 2026-06-25 10:08 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53181?
CVE-2026-53181 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: vsock/vmci: fix skackbacklog leak on failed handshake When vmcitransportrecvconnectingserver() returns an error, vmcitransportrecvlisten() calls vsockremove_pending() but never calls skacceptqremoved(). This leaves skackbacklog…
When was CVE-2026-53181 disclosed?
CVE-2026-53181 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-53181 actively exploited?
CVE-2026-53181 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53181?
CVE-2026-53181 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53181?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53181, 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-53181

Explore →

Is Your Infrastructure Affected by CVE-2026-53181?

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