CVE-2025-37899: ksmbd: fix use-after-free in session logoff
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in session logoff
The sess->user object can currently be in use by another thread, for
example if another connection has sent a session setup request to
bind to the session being free'd. The handler for that connection could
be in the smb2_sess_setup function which makes use of sess->user.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux kernel’s ksmbd SMB file-sharing server can cause it to use a user-session object after that object is freed. A network-connected user with limited privileges may be able to trigger memory corruption, potentially compromising confidentiality, integrity, and availability. Systems not running ksmbd are unlikely to be exposed.
Executive priority
Prioritize affected internet-facing or broadly reachable ksmbd servers for urgent assessment and patching. Treat internal servers as high priority where untrusted or compromised users can authenticate. Systems without ksmbd can be documented as not exposed after configuration and runtime validation.
Technical view
During SMB session logoff, ksmbd may free sess->user while another thread processes a session-setup request that binds another connection to the same session. That thread can subsequently access the freed object. The supplied CVSS 3.1 score is 8.8, with network reachability, low complexity, low privileges, no user interaction, and high impacts.
Likely exposure
Exposure requires a Linux system using ksmbd and network access to its SMB service. The supplied affected-version data includes several kernel branches and releases but is not sufficiently clear to establish precise vulnerable ranges. Distribution backports may also change status, so assess the running vendor kernel rather than relying solely on its version number.
Exploitation context
The source bundle identifies remote network reachability with low privileges and low attack complexity. A public researcher described discovering the issue as a remote zero-day. However, the CVE is not listed as KEV in the bundle, and the supplied evidence does not establish active exploitation or a publicly usable exploit.
Researcher notes
The defect is a concurrent session-lifecycle error involving logoff and session binding. Stable-kernel references document fixes across branches. Precise affected and fixed release boundaries are ambiguous in the supplied version list; confirm commit inclusion or distribution backports. The sources support serious potential impact but do not prove reliable exploitation or exploitation in the wild.
Mitigation direction
Install a vendor-supported kernel containing the applicable stable fix or backport.
Consult the Linux distribution’s advisory to map its package versions to the fix.
Disable ksmbd where SMB file sharing is unnecessary.
Restrict SMB access to trusted networks and authenticated users until patched.
Validation and detection
Confirm whether ksmbd is installed, enabled, loaded, or actively serving SMB.
Identify the running kernel and its distribution package release.
Verify vendor documentation confirms inclusion of the relevant stable fix or backport.
Check network controls limit SMB reachability to required trusted clients.
After updating, confirm the fixed kernel is running, not merely installed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-37899 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.