CVE-2025-38321
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-11-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-NVD-CWE-noinfo |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's SMB (CIFS) implementation. Under low-memory conditions, the function close_all_cached_dirs() fails to move dentries to a separate list for proper cleanup after locks are dropped. This results in a 'Dentry still in use' error, which can cause warnings and potential issues during unmounting of CIFS shares. The fix involves logging a clear error message when this failure happens and stopping further attempts to allocate memory for subsequent tcons when an allocation fails.
How can this vulnerability impact me? :
This vulnerability can cause errors and warnings related to dentries still being in use during unmounting of CIFS shares, especially under low-memory conditions. This may lead to instability or unexpected behavior in the filesystem operations involving SMB shares, potentially affecting system reliability or causing resource leaks.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring system logs for specific error messages related to CIFS and dentries under low-memory conditions. Look for log entries such as: "CIFS: VFS: \\otters.example.com\share Out of memory while dropping dentries" and "BUG: Dentry ... still in use". You can use commands like `dmesg | grep -i 'CIFS'` or `journalctl -k | grep -i 'dentry'` to find these errors in kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include ensuring your system is running a Linux kernel version that includes the fix for this issue. Additionally, monitor system memory usage to avoid low-memory conditions that trigger this problem. If possible, update the kernel to the patched version where the error logging and bailout on allocation failure have been implemented.