CVE-2025-71153
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-02-26
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.7.12 (inc) to 6.8 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.4 (exc) |
| linux | linux_kernel | From 6.6.24 (inc) to 6.6.120 (exc) |
| linux | linux_kernel | From 6.8.3 (inc) to 6.12.64 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's ksmbd component within the get_file_all_info() function. Specifically, if the vfs_getattr() call fails, the function returns immediately without freeing the allocated filename memory, causing a memory leak. The fix involves freeing the filename before returning in this error case.
How can this vulnerability impact me? :
The memory leak caused by this vulnerability can lead to increased memory usage over time, potentially degrading system performance or causing resource exhaustion if exploited repeatedly. This could affect system stability and reliability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the ksmbd get_file_all_info() memory leak has been fixed. This involves applying the patch that frees the allocated filename when vfs_getattr() fails. Until the update is applied, monitor for unusual memory usage in ksmbd processes as a precaution.