Linux kernel memory leak in ksmbd via compounded SMB session setup
- Exploited
- No known exploitation
- Fix
- Fixed in 5.16, 6.2, 6.7, 6.12
- Who is exposed
- Not reported
Summary
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix session reference leak on compounded SESSION_SETUP
A compound request can place SESSION_SETUP after another command. That earlier command leaves a reference to its session in work->sess. smb2_sess_setup() then overwrites work->sess with the session it looks up or creates, and the dispatcher later puts work->sess only once. The inherited reference is never dropped. That leaks the session, together with its setup connection and socket, and every repeat of the compound leaks another.
unreferenced object (size 512): __kmalloc_cache_noprof+0x32c/0x3a0 ksmbd_smb2_session_create+0xf6/0x9c0 [ksmbd] smb2_sess_setup+0xda4/0x6280 [ksmbd] handle_ksmbd_work+0x88c/0x1cb0 [ksmbd]
Save the inherited session on entry. After the request has been processed, release it once, but only when smb2_sess_setup() has replaced work->sess with its own session or cleared it. Do this after ksmbd_conn_unlock() so the put does not run under srv_mutex. An error path may instead leave the inherited session in work->sess. Keep it there, so the dispatcher still puts it and the error response is still signed or encrypted with it as before.
What to do
Upgrade to a fixed version: 5.16, 6.2, 6.7, 6.12.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99539 (ksmbd: fix session reference leak on compounded SESSION_SETUP), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99539 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 5.15.171, fixed in 5.16; from 6.1.114, fixed in 6.2; from 6.6.58, fixed in 6.7; from 6.11.5, fixed in 6.12
- Linux Linux: versions 6.12
Fixed versions: 5.16, 6.2, 6.7, 6.12.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99539 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99539 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/b2d710b12e86fd4cf02be090651fa6ea8683fc29
- https://git.kernel.org/stable/c/38cddb9f7c9102f23652d198748c658072cf0df5
- https://git.kernel.org/stable/c/db30f8f330fc73304edfe595dc5a6f5e17ba97f2
- https://git.kernel.org/stable/c/03bd8f5279e490e15e0c0f0fa388ffbd2fbacd65
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99539
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99539"}.Affected versions
- Linux LinuxFrom 5.15.171 · fixed in 5.16; From 6.1.114 · fixed in 6.2; From 6.6.58 · fixed in 6.7; From 6.11.5 · fixed in 6.12
- Linux Linux6.12
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99539 |
| Record | NVD · CVE-2026-99539 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/b2d710b12e86fd4cf02be090651fa6ea8683fc29 |
| Link | git.kernel.org · stable/c/38cddb9f7c9102f23652d198748c658072cf0df5 |
| Link | git.kernel.org · stable/c/db30f8f330fc73304edfe595dc5a6f5e17ba97f2 |
| Link | git.kernel.org · stable/c/03bd8f5279e490e15e0c0f0fa388ffbd2fbacd65 |
Questions about CVE-2026-99539
Is CVE-2026-99539 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99539?
Linux: from 5.15.171 before 5.16; from 6.1.114 before 6.2; from 6.6.58 before 6.7; from 6.11.5 before 6.12. Linux: version 6.12.
Source: cve.now feed data
How do I fix CVE-2026-99539?
Upgrade to a fixed version: 5.16, 6.2, 6.7, 6.12.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.