CVE-2026-31711

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.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:

smb: server: fix active_num_conn leak on transport allocation failure

Commit 77ffbcac4e56 ("smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()") addressed the kthread_run() failure path. The earlier alloc_transport() == NULL path in the same function has the same leak, is reachable pre-authentication via any TCP connect to port 445, and was empirically reproduced on UML (ARCH=um, v7.0-rc7): a small number of forced allocation failures were sufficient to put ksmbd into a state where every subsequent connection attempt was rejected for the remainder of the boot.

ksmbd_kthread_fn() increments active_num_conn before calling ksmbd_tcp_new_connection() and discards the return value, so when alloc_transport() returns NULL the socket is released and -ENOMEM returned without decrementing the counter. Each such failure permanently consumes one slot from the max_connections pool; once cumulative failures reach the cap, atomic_inc_return() hits the threshold on every subsequent accept and every new connection is rejected. The counter is only reset by module reload.

An unauthenticated remote attacker can drive the server toward the memory pressure that makes alloc_transport() fail by holding open connections with large RFC1002 lengths up to MAX_STREAM_PROT_LEN (0x00FFFFFF); natural transient allocation failures on a loaded host produce the same drift more slowly.

Mirror the existing rollback pattern in ksmbd_kthread_fn(): on the alloc_transport() failure path, decrement active_num_conn gated on server_conf.max_connections.

Repro details: with the patch reverted, forced alloc_transport() NULL returns leaked counter slots and subsequent connection attempts -- including legitimate connects issued after the forced-fail window had closed -- were all rejected with "Limit the maximum number of connections". With this patch applied, the same connect sequence produces no rejections and the counter cycles cleanly between zero and one on every accept.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
41.7%
KEV
Not listed

Published

May 1, 2026

Last Modified

June 19, 2026

Advisory Details (5)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

smb: server: fix active_num_conn leak on transport allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

smb: server: fix active_num_conn leak on transport allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97f8d2648ef4871e4cd335e2d769cb40054a6772
generic

smb: server: fix active_num_conn leak on transport allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6551300dc452ac16a855a83dbd1e74899542d3b3
generic

smb: server: fix active_num_conn leak on transport allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/295a9fc6789d1011c36ded9f0f2907bb34fa0de4
generic

smb: server: fix active_num_conn leak on transport allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/283027aa93380380a0994f35dde3ec95318f2654

Vendor Advisories for CVE-2026-31711(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 9× in last 7d / 47× 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 161 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-31711?
CVE-2026-31711 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: smb: server: fix activenumconn leak on transport allocation failure Commit 77ffbcac4e56 ("smb: server: fix leak of activenumconn in ksmbdtcpnewconnection()") addressed the kthreadrun() failure path. The earlier alloc_transport() ==…
When was CVE-2026-31711 disclosed?
CVE-2026-31711 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31711 actively exploited?
CVE-2026-31711 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31711?
CVE-2026-31711 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-31711?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31711, 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-31711

Explore →

Is Your Infrastructure Affected by CVE-2026-31711?

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