In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix Preauh_HashValue race condition
If client send multiple session setup requests to ksmbd,
Preauh_HashValue race condition could happen.
There is no need to free sess->Preauh_HashValue at session setup phase.
It can be freed together with session at connection termination phase.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux kernel’s ksmbd SMB server can occur when multiple session-setup requests overlap. The supplied CVSS rating is 9.8, reflecting potentially severe confidentiality, integrity, and availability impact. Exposure requires ksmbd to be present, enabled, and reachable. The supplied evidence does not confirm real-world exploitation.
Executive priority
Treat reachable ksmbd servers as an urgent patching priority because the supplied rating is critical and authentication is not required. Internet-facing or broadly accessible SMB services should be addressed first. Systems without ksmbd enabled are unlikely to expose this specific flaw. Confirm vendor backports before declaring systems vulnerable or remediated.
Technical view
Concurrent ksmbd session-setup requests can race around sess->Preauth_HashValue lifecycle handling. The kernel fix avoids freeing this value during session setup and instead releases it with the session when the connection terminates. The record classifies the flaw as CWE-362 and network-accessible without privileges or user interaction, although demonstrated impact is not detailed in the supplied description.
Likely exposure
Prioritize Linux systems running an affected kernel with ksmbd enabled and SMB reachable from untrusted networks. The supplied version list includes 5.15 and several 6.x releases, but does not clearly express complete range boundaries. Distribution backports may change exposure, so verify package-specific status and fix inclusion rather than relying only on version strings.
Exploitation context
The supplied record is not in CISA KEV, and no provided evidence establishes active exploitation. The documented trigger involves overlapping session-setup requests. The CVSS vector indicates remote, unauthenticated, low-complexity reachability, but the bundle does not document a public proof of concept, observed attacks, or reliably demonstrated outcomes.
Researcher notes
The source bundle supports a Preauth_HashValue lifetime race and a fix deferring release until connection termination. It does not establish whether exploitation yields memory corruption, code execution, information disclosure, or only denial of service. The listed affected versions are ambiguous and include duplicated commit data, so use kernel or distribution fix provenance for precise assessment.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable stable fix.
Check distribution security guidance for backported fixes and corrected package versions.
Restrict SMB access to trusted networks while remediation is pending.
Disable ksmbd where it is unnecessary and operationally safe.
Validation and detection
Inventory systems where ksmbd is installed, loaded, or configured to start.
Confirm whether SMB endpoints are reachable from untrusted or internet-facing networks.
Compare each running kernel against distribution advisories and applicable stable fix commits.
After updating, verify the running kernel includes the fix and ksmbd services restarted appropriately.
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.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.