CVE-2025-71204: smb/server: fix refcount leak in parse_durable_handle_context()
In the Linux kernel, the following vulnerability has been resolved:
smb/server: fix refcount leak in parse_durable_handle_context()
When the command is a replay operation and -ENOEXEC is returned,
the refcount of ksmbd_file must be released.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a reference-count leak in the in-kernel SMB server. Under a replay-operation error path, the kernel fails to release a file reference. The public record does not provide CVSS, confirmed impact, or active exploitation evidence.
Executive priority
Handle as a monitored kernel maintenance item unless ksmbd is deployed on exposed servers. There is no public exploitation evidence in the bundle, but SMB-facing kernel code deserves timely patch validation once vendor packages are available.
Technical view
CVE-2025-71204 affects Linux ksmbd. In parse_durable_handle_context(), a replay operation returning -ENOEXEC can leave a ksmbd_file reference unreleased. The kernel stable fixes release the reference on that path. Source data does not describe privilege requirements, remote reachability, or crashability.
Likely exposure
Exposure is most relevant to Linux systems using the kernel SMB server, ksmbd. The bundle lists Linux as affected but does not clearly map all vulnerable release ranges to distribution packages. Systems not running ksmbd are less likely to exercise this code path.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. The record describes a fixed bug, not an exploit scenario. Treat exploitability as unproven from the available evidence.
Researcher notes
The key uncertainty is impact. A refcount leak may imply resource retention, but the record does not prove denial of service, privilege escalation, or remote exploitability. Analysis should focus on ksmbd replay handling and whether reachable requests can repeatedly trigger -ENOEXEC.
Mitigation direction
Apply Linux kernel updates that include the referenced stable fixes.
Check your distribution advisory for CVE-2025-71204 package status.
Disable ksmbd where the in-kernel SMB server is not required.
Restrict SMB exposure to trusted networks where business requirements allow.
Track vendor guidance because CVSS and impact details are incomplete.
Validation and detection
Inventory Linux hosts and kernel versions running SMB services.
Confirm whether ksmbd is loaded or enabled on each system.
Compare installed kernel packages with distribution CVE advisories.
Verify kernel changelogs include one of the referenced stable commits.
Prioritize internet-exposed or untrusted-network SMB servers for review.
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-71204 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 14, 2026, 16:27 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.