CVE-2026-31711smb: server: fix active_num_conn leak on transport allocation failure
- 7.5HighCVSS base score
- 0.55%Exploitation in 30 daysEPSS · top 53% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 53 days later
· 53 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.55% · top 53% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 4210c3555db4b38bade92331b153e583261f05f9 – < dc2e7d595d68cf1be1ba64e3d30ebf3266bf7242
- affected d5d7847e57ac69fa99c18b363a34419bcdb5a281 – < 60734c8bc3b4aa0672e251f08dda81977e4b5387
- affected 0d0d4680db22eda1eea785c47bbf66a9b33a8b16 – < 97f8d2648ef4871e4cd335e2d769cb40054a6772
- affected 0d0d4680db22eda1eea785c47bbf66a9b33a8b16 – < 295a9fc6789d1011c36ded9f0f2907bb34fa0de4
- affected 0d0d4680db22eda1eea785c47bbf66a9b33a8b16 – < 283027aa93380380a0994f35dde3ec95318f2654
- affected 0d0d4680db22eda1eea785c47bbf66a9b33a8b16 – < fb48185bcd946d42de7017cf27f912f8ab26acf0
- affected 0d0d4680db22eda1eea785c47bbf66a9b33a8b16 – < 6551300dc452ac16a855a83dbd1e74899542d3b3
- affected 5.15.91 – < 5.15.210
- affected 6.1.9 – < 6.1.175
- affected 6.2
- unaffected < 6.2
- unaffected 5.15.210 – ≤ 5.15.*
- unaffected 6.1.175 – ≤ 6.1.*
- unaffected 6.6.136 – ≤ 6.6.*
- unaffected 6.12.84 – ≤ 6.12.*
- unaffected 6.18.25 – ≤ 6.18.*
- unaffected 7.0.2 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References8
- https://git.kernel.org/stable/c/dc2e7d595d68cf1be1ba64e3d30ebf3266bf7242 (opens in a new tab)
- https://git.kernel.org/stable/c/60734c8bc3b4aa0672e251f08dda81977e4b5387 (opens in a new tab)
- https://git.kernel.org/stable/c/97f8d2648ef4871e4cd335e2d769cb40054a6772 (opens in a new tab)
- https://git.kernel.org/stable/c/295a9fc6789d1011c36ded9f0f2907bb34fa0de4 (opens in a new tab)
- https://git.kernel.org/stable/c/283027aa93380380a0994f35dde3ec95318f2654 (opens in a new tab)
- https://git.kernel.org/stable/c/fb48185bcd946d42de7017cf27f912f8ab26acf0 (opens in a new tab)
- https://git.kernel.org/stable/c/6551300dc452ac16a855a83dbd1e74899542d3b3 (opens in a new tab)
- https://cert-portal.siemens.com/productcert/html/ssa-784472.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-26520 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31711)Record last updated .