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

A fix is available — apply it.

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.

Patch Availability(4)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 45× 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.

Showing the most recent 100 of 209 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 07:38 UTCEG score recompute
  4. 2026-09-18 07:38 UTCVendor advisory
  5. 2026-09-18 07:38 UTCGHSA enrichment
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-14 01:26 UTCEG score recompute
  9. 2026-09-14 01:26 UTCVendor advisory
  10. 2026-09-14 01:26 UTCGHSA enrichment
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-12 15:59 UTCEG score recompute
  13. 2026-09-12 15:59 UTCVendor advisory
  14. 2026-09-12 15:59 UTCGHSA enrichment
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 16:01 UTCEPSS rescore
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-30 19:41 UTCEG score recompute
  25. 2026-08-30 19:41 UTCVendor advisory
Show 75 more
  1. 2026-08-30 19:41 UTCGHSA enrichment
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-28 02:55 UTCEG score recompute
  6. 2026-08-28 02:55 UTCVendor advisory
  7. 2026-08-28 02:55 UTCGHSA enrichment
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 14:16 UTCEG score recompute
  12. 2026-08-24 14:16 UTCVendor advisory
  13. 2026-08-24 14:16 UTCGHSA enrichment
  14. 2026-08-23 12:34 UTCEG score recompute
  15. 2026-08-23 12:34 UTCVendor advisory
  16. 2026-08-23 12:34 UTCGHSA enrichment
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 10:54 UTCEG score recompute
  19. 2026-08-22 10:54 UTCVendor advisory
  20. 2026-08-22 10:54 UTCGHSA enrichment
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-21 09:11 UTCEG score recompute
  23. 2026-08-21 09:11 UTCVendor advisory
  24. 2026-08-21 09:11 UTCGHSA enrichment
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-20 07:11 UTCEG score recompute
  27. 2026-08-20 07:11 UTCVendor advisory
  28. 2026-08-20 07:11 UTCGHSA enrichment
  29. 2026-08-19 17:04 UTCEPSS rescore
  30. 2026-08-19 01:34 UTCEG score recompute
  31. 2026-08-19 01:34 UTCVendor advisory
  32. 2026-08-19 01:34 UTCGHSA enrichment
  33. 2026-08-18 13:48 UTCEPSS rescore
  34. 2026-08-17 13:47 UTCEPSS rescore
  35. 2026-08-17 11:55 UTCEG score recompute
  36. 2026-08-17 11:55 UTCVendor advisory
  37. 2026-08-17 11:55 UTCGHSA enrichment
  38. 2026-08-16 14:56 UTCEPSS rescore
  39. 2026-08-16 10:15 UTCEG score recompute
  40. 2026-08-16 10:15 UTCVendor advisory
  41. 2026-08-16 10:15 UTCGHSA enrichment
  42. 2026-08-16 02:14 UTCEPSS rescore
  43. 2026-08-15 08:35 UTCEG score recompute
  44. 2026-08-15 08:35 UTCVendor advisory
  45. 2026-08-15 08:35 UTCGHSA enrichment
  46. 2026-08-15 01:30 UTCEPSS rescore
  47. 2026-08-14 06:36 UTCEG score recompute
  48. 2026-08-14 06:36 UTCVendor advisory
  49. 2026-08-14 06:36 UTCGHSA enrichment
  50. 2026-08-13 22:00 UTCEPSS rescore
  51. 2026-08-13 04:55 UTCEG score recompute
  52. 2026-08-13 04:55 UTCGHSA enrichment
  53. 2026-08-12 13:51 UTCEPSS rescore
  54. 2026-08-12 03:15 UTCEG score recompute
  55. 2026-08-12 03:15 UTCVendor advisory
  56. 2026-08-12 03:15 UTCGHSA enrichment
  57. 2026-08-11 01:34 UTCEG score recompute
  58. 2026-08-11 01:34 UTCVendor advisory
  59. 2026-08-11 01:34 UTCGHSA enrichment
  60. 2026-08-11 00:00 UTCEPSS rescore
  61. 2026-08-09 23:53 UTCEG score recompute
  62. 2026-08-09 23:53 UTCGHSA enrichment
  63. 2026-08-09 13:46 UTCEPSS rescore
  64. 2026-08-08 22:13 UTCEG score recompute
  65. 2026-08-08 22:13 UTCVendor advisory
  66. 2026-08-08 22:13 UTCGHSA enrichment
  67. 2026-08-08 16:37 UTCEPSS rescore
  68. 2026-08-07 20:32 UTCEG score recompute
  69. 2026-08-07 20:32 UTCGHSA enrichment
  70. 2026-08-06 18:52 UTCEG score recompute
  71. 2026-08-06 18:52 UTCVendor advisory
  72. 2026-08-06 18:52 UTCGHSA enrichment
  73. 2026-08-06 13:47 UTCEPSS rescore
  74. 2026-08-05 19:17 UTCEPSS rescore
  75. 2026-08-05 17:12 UTCEG score recompute

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

See which npm, PyPI, Go, and Maven packages are affected by 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.