CVE-2025-71153: ksmbd: Fix memory leak in get_file_all_info()
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: Fix memory leak in get_file_all_info()
In get_file_all_info(), if vfs_getattr() fails, the function returns
immediately without freeing the allocated filename, leading to a memory
leak.
Fix this by freeing the filename before returning in this error case.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a memory leak in ksmbd, the in-kernel SMB server. A failed file-attribute lookup can leave an allocated filename in memory. The business risk appears availability-focused, but the source bundle provides no CVSS score, severity rating, or exploitation evidence.
Executive priority
Treat as a routine kernel maintenance item unless ksmbd is internet-exposed or business-critical. Prioritize patch validation on SMB-serving Linux hosts, but do not assume emergency exploitation without stronger evidence.
Technical view
In get_file_all_info(), an error return from vfs_getattr() skipped cleanup of an allocated filename. The stable kernel fixes free that memory before returning. The affected component is Linux ksmbd; exact distribution exposure depends on kernel branch, backports, and whether ksmbd is enabled.
Likely exposure
Linux systems running kernels with ksmbd available and enabled are the relevant exposure group. Systems not using ksmbd are unlikely to reach this code path. Distribution kernels require vendor-specific mapping because backports may change version conclusions.
Exploitation context
The provided sources do not show active exploitation, KEV listing, public exploit code, or weaponized details. Based on the description, impact is most plausibly resource leakage and availability degradation if an attacker can repeatedly trigger the error path.
Researcher notes
Evidence is limited to the CVE description and kernel stable commit references. There is no CVSS, CWE, or exploitability analysis in the bundle. Focus review on ksmbd deployments and whether vfs_getattr() failure can be induced remotely in affected builds.
Mitigation direction
Check Linux distribution advisories for CVE-2025-71153 mapping.
Update to a kernel containing the referenced stable fixes.
Disable ksmbd if SMB serving is not required.
Restrict SMB exposure to trusted networks where operationally possible.
Validation and detection
Inventory Linux hosts and kernel versions.
Confirm whether the ksmbd module or service is enabled.
Map installed kernels against vendor advisories and backports.
Review change logs for the referenced stable commits.
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-71153 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.
Jan 23, 2026, 14:25 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.