CVE-2024-35862: smb: client: fix potential UAF in smb2_is_network_name_deleted()
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix potential UAF in smb2_is_network_name_deleted()
Skip sessions that are being teared down (status == SES_EXITING) to
avoid UAF.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s SMB client can access a session after it has begun shutting down, creating a use-after-free memory-safety risk. The supplied CVSS score is 9.8, indicating potentially severe confidentiality, integrity, and availability impact, but the sources do not document a demonstrated attack outcome.
Executive priority
Treat as an urgent patching and exposure-verification issue for SMB-using Linux systems. Critical scoring warrants prompt action, but the absence of documented exploitation means priority should remain risk-based rather than emergency incident response unless local evidence suggests abuse.
Technical view
smb2_is_network_name_deleted() could examine a session being torn down, potentially using freed memory. The kernel fix skips sessions whose status is SES_EXITING. The supplied sources identify the flaw and corrective commits but do not establish exploitability details or reliable fixed-version boundaries across distributions.
Likely exposure
Exposure applies to Linux systems using the kernel SMB client, especially those connecting to SMB shares. The bundle lists 5.12, 6.1.85, 6.6.26, 6.8.5, and 6.9 as affected, plus an ambiguous “0” entry. Distribution backports may change actual status.
Exploitation context
The bundle marks this CVE as absent from CISA KEV and provides no evidence of active exploitation or a public exploit. Although the supplied CVSS vector rates it network-accessible without privileges or user interaction, the sources do not explain the conditions needed to trigger the teardown race.
Researcher notes
The narrow documented defect is session-lifetime handling: SES_EXITING sessions must be ignored to prevent a potential use-after-free. The source bundle does not provide trigger mechanics, crash signatures, proof of code execution, affected distribution packages, or complete version-range semantics. Avoid extending conclusions beyond the SMB client teardown path.
Mitigation direction
Apply a supported vendor kernel update containing the referenced SMB client fix.
Prioritize systems that mount or regularly access SMB shares.
Check distribution advisories because patched kernels may retain older version numbers.
If patching is delayed, reduce unnecessary SMB client connectivity and monitor vendor guidance.
Validation and detection
Inventory kernel versions on systems using SMB client functionality.
Identify active and configured SMB mounts, including automated mounts.
Confirm vendor packages backport one of the referenced corrective commits.
After updating, verify the patched kernel is running following any required reboot.
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-2024-35862 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.
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.