CVE-2025-39825: smb: client: fix race with concurrent opens in rename(2)
In the Linux kernel, the following vulnerability has been resolved:
smb: client: fix race with concurrent opens in rename(2)
Besides sending the rename request to the server, the rename process
also involves closing any deferred close, waiting for outstanding I/O
to complete as well as marking all existing open handles as deleted to
prevent them from deferring closes, which increases the race window
for potential concurrent opens on the target file.
Fix this by unhashing the dentry in advance to prevent any concurrent
opens on the target.
Security readout for executives and security teams
Plain-English summary
A race condition in the Linux SMB client can occur when one process renames a file while another opens the rename target. A local, low-privileged user could potentially trigger serious confidentiality, integrity, or availability impact. Exposure depends on affected kernels, SMB client use, and concurrent file operations.
Executive priority
Treat as a high-priority kernel update for multi-user systems and SMB-dependent servers. Accelerate remediation where untrusted local users can access SMB mounts. Internet-only exposure is not indicated by the local attack vector, so prioritize by actual SMB client use and local access paths.
Technical view
During rename handling, the SMB client closes deferred handles, waits for I/O, and marks existing handles deleted. This creates a window for concurrent opens on the target dentry. The kernel fix unhashes that dentry before these operations, preventing new opens during the vulnerable window.
Likely exposure
Prioritize Linux systems using SMB-mounted storage where untrusted or low-privileged local users can perform file operations. The supplied record identifies affected versions including 5.13 through several 6.x releases, but its version data is ambiguous; confirm applicability through kernel or distribution advisories.
Exploitation context
The CVSS vector requires local access and low privileges, with no user interaction. The supplied record is not in CISA KEV, and the sources provided do not establish active exploitation or public weaponization. Practical triggering also appears to require concurrent SMB rename and open activity.
Researcher notes
The record describes a synchronization flaw around target dentries and concurrent opens, but supplies no CWE or demonstrated exploitation details. Validate backports by code change or vendor changelog, not version numbers alone. The upstream remediation unhashes the target dentry before rename cleanup to close the race window.
Mitigation direction
Install the corrected kernel package supplied by the system vendor or Linux distribution.
Confirm the update includes the applicable upstream stable fix for the running kernel branch.
Where immediate patching is impossible, restrict untrusted local access to SMB-mounted paths.
Review Debian or appliance-vendor advisories when those products are deployed.
Validation and detection
Inventory running kernel versions and identify hosts using the Linux SMB client.
Compare vendor package changelogs against CVE-2025-39825 and the referenced stable commits.
After updating, reboot if required and verify the corrected kernel is running.
Run safe SMB rename-and-open regression tests in an isolated environment.
Monitor affected hosts for crashes or abnormal SMB file-operation failures.
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-39825 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.