CVE-2025-37924: ksmbd: fix use-after-free in kerberos authentication
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix use-after-free in kerberos authentication
Setting sess->user = NULL was introduced to fix the dangling pointer
created by ksmbd_free_user. However, it is possible another thread could
be operating on the session and make use of sess->user after it has been
passed to ksmbd_free_user but before sess->user is set to NULL.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux kernel SMB server, ksmbd, can let one thread use Kerberos session data after another thread frees it. The supplied rating indicates possible confidentiality, integrity, and availability impact. Exposure depends on whether ksmbd and Kerberos authentication are actually enabled.
Executive priority
Treat confirmed ksmbd-plus-Kerberos deployments as urgent patching candidates, especially when SMB is reachable from untrusted networks. Systems using another SMB implementation or not using ksmbd require verification before prioritization. Current sources do not justify claiming an active attack campaign.
Technical view
During concurrent Kerberos authentication processing, ksmbd may call ksmbd_free_user on sess->user before setting that pointer to NULL. Another thread can dereference the freed object during this interval, causing a use-after-free. The supplied CVSS 3.1 score is 9.8 with network, low-complexity, unauthenticated, no-interaction characteristics.
Likely exposure
Prioritize Linux hosts running the in-kernel ksmbd SMB server with Kerberos authentication. The CVE record lists affected Linux kernel releases including 5.15, 6.1.138, 6.6.90, 6.12.28, 6.14.6, and 6.15. Distribution backports may change exposure, so kernel version alone may be insufficient.
Exploitation context
The supplied record is not in KEV, and the sources provide no evidence of active exploitation or a public exploit. The CVSS vector describes network-reachable, unauthenticated potential, but it does not establish practical exploit reliability. Successful triggering appears dependent on concurrent session activity reaching the race window.
Researcher notes
The defect is a narrow concurrency window between freeing sess->user and clearing the pointer. The record supplies multiple stable-tree fixes but no CWE classification, crash signature, proof of concept, or demonstrated exploitation outcome. Assess distribution-specific backports and configuration before drawing exposure conclusions.
Mitigation direction
Apply a supported vendor kernel update that incorporates the referenced ksmbd fix.
Confirm distribution advisories because vendors may backport fixes without changing upstream version numbers.
If patching is delayed, consult vendor guidance for supported temporary exposure-reduction measures.
Prioritize internet-facing or broadly reachable SMB servers using ksmbd and Kerberos.
Validation and detection
Inventory systems where ksmbd is installed, loaded, enabled, or serving SMB traffic.
Determine whether affected ksmbd deployments use Kerberos authentication.
Compare running kernel packages with current distribution security advisories for CVE-2025-37924.
Verify package changelogs or source history include the applicable referenced stable-kernel fix.
Retest service availability and Kerberos authentication after updating.
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-37924 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
7Source 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.