CVE-2026-53181

MEDIUMNVD 5.55.5
EchelonGraph scoreHIGH 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 — 5 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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(high)
EPSS
8.2%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

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 18× in last 7d / 29× 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-06 19:48 UTCEG score recompute 5.50
  2. 2026-07-06 19:48 UTCVendor advisory
  3. 2026-07-06 19:47 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 13:06 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-03 23:14 UTCVendor advisory
  14. 2026-07-03 23:13 UTCGHSA enrichment
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 02:50 UTCVendor advisory
  17. 2026-07-01 02:50 UTCGHSA enrichment
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-29 14:06 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 06:29 UTCEG score recompute
  23. 2026-06-28 06:29 UTCGHSA enrichment
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 04:56 UTCEPSS rescore
Show 4 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-25 10:08 UTCEG score recompute
  4. 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 8.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.