CVE-2024-46736: smb: client: fix double put of @cfile in smb2_rename_path()
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix double put of @cfile in smb2_rename_path()
If smb2_set_path_attr() is called with a valid @cfile and returned
-EINVAL, we need to call cifs_get_writable_path() again as the
reference of @cfile was already dropped by previous smb2_compound_op()
call.
Security readout for executives and security teams
Plain-English summary
CVE-2024-46736 is a Linux kernel SMB client bug involving incorrect handling of an internal file reference during a rename path error case. The public record does not provide CVSS, CWE, or a clear impact statement. Treat it as a kernel maintenance issue, with higher attention on systems that mount SMB/CIFS shares.
Executive priority
Schedule remediation through normal kernel patch governance, elevating priority for SMB-dependent servers and workstations. There is no source-backed evidence of active exploitation, but kernel reference-counting flaws can affect reliability and should not be left unmanaged.
Technical view
The Linux SMB/CIFS client could double-release cfile in smb2_rename_path() when smb2_set_path_attr() returned -EINVAL after smb2_compound_op() had already dropped the reference. The fix reacquires a writable path before continuing. Public sources identify the code defect and fixes but do not state exploitability or concrete impact.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions that use the SMB/CIFS client to mount or operate on SMB shares. Systems not using the kernel SMB client are less likely exposed. The bundle’s affected version data is incomplete and should be verified against vendor kernel packages.
Exploitation context
CISA KEV status is false, and the supplied sources do not report active exploitation or public exploit activity. The bundle does not describe attacker prerequisites, required privileges, or reachable impact, so exploitation likelihood cannot be reliably rated from these sources alone.
Researcher notes
The source bundle supports a narrow conclusion: an SMB client reference handling bug was fixed in Linux stable commits. It does not provide CVSS, CWE, crash details, exploitability analysis, or vendor package mapping. Further assessment should focus on affected kernel branch ranges and distro backports.
Mitigation direction
Update affected Linux kernels using distribution or vendor-supported packages.
Prioritize hosts that mount SMB/CIFS shares or run file services depending on them.
Review kernel stable commits linked in the CVE record for fixed branches.
Check Linux distribution advisories for backported fixes and package-specific version mapping.
Validation and detection
Inventory Linux hosts using SMB/CIFS mounts or related automation.
Compare running kernel package versions with distribution advisory fixed versions.
Confirm the relevant stable kernel fix is present in source or package changelog.
Monitor logs for SMB/CIFS client instability, while recognizing logs cannot prove exposure.
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-46736 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.