Security readout for executives and security teams
Plain-English summary
A Linux SMB client race can free hostname memory twice while a CIFS connection is shutting down and reconnecting across DFS targets. This can corrupt kernel memory and crash the system. The supplied record rates it critical, but the evidence does not establish remote code execution or real-world attacks.
Executive priority
Treat as an urgent kernel-maintenance issue for Linux systems using SMB/CIFS with DFS. Patch those systems first, then validate broader fleet exposure. Avoid assuming every Linux host is immediately exploitable: the documented failure requires a particular reconnect-and-shutdown race, and exploitation evidence is absent.
Technical view
CVE-2025-21673 is a CWE-415 double free in the Linux CIFS client. cifs_put_tcp_session() could release TCP_Server_Info::hostname before the cifsd thread finished reconnecting to multiple DFS targets. A subsequent reconnect could reuse or free that memory, producing kernel memory corruption and a slab-free fault.
Likely exposure
Exposure is most likely on affected Linux kernels actively using the CIFS/SMB client with DFS targets, particularly during concurrent session shutdown and reconnection. The supplied version data is not a clear contiguous range, so organizations should map their distribution kernel package to vendor guidance and the referenced stable fixes.
Exploitation context
The bundle reports no known active exploitation, and the CVE is not listed as KEV. The demonstrated outcome is a kernel fault during a specific CIFS DFS reconnection race. Although the supplied CVSS is 9.8, the sources provided do not demonstrate remote code execution, data theft, or reliable attacker control.
Researcher notes
The affected-version entries contain commit identifiers, isolated releases, and an ambiguous “0,” preventing a dependable range interpretation. The trace supports a double free in CIFS DFS reconnection and a kernel crash. Further conclusions about attacker reachability, exploitation primitives, or confidentiality and integrity impact are not established by the supplied sources.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable referenced stable fix.
Check Linux distribution advisories for package-specific affected and fixed versions.
Prioritize systems using CIFS mounts and DFS namespaces.
Follow vendor guidance if an updated kernel is not immediately available.
Validation and detection
Record each system's running kernel and distribution package version.
Identify hosts with the CIFS module loaded or active SMB mounts.
Determine whether mounted SMB resources use DFS targets.
Map deployed packages against vendor advisories and referenced stable commits.
After updating, confirm the fixed kernel is running following reboot.
Review kernel logs for CIFS reconnect and slab-free fault signatures.
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-415: 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.
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.