CVE-2025-38321

smb: Log an error when close_all_cached_dirs fails

MEDIUM
5.5
CVSS Score
Published: July 10, 2025 at 08:14 AM UTC
Updated: October 15, 2026 at 10:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.6.956.13 ≤ v < 6.15.46.7 ≤ v < 6.12.353fa640d035e5ae526769615c35cb9ed4be6e3662548812afd96982a76a93ba76c0582ea670c40d9e6.11.116.12.26.166.16 rc16.16 rc26.6.6473934e535cffbda1490fa97d82690a0f9aa73e94ff4528bbc82d0d90073751f7b49e7b9e9c7e5638
Vendor states this is fixed in 43f26094d6702e494e800532c3f1606e7a68eb30 (fixed)
Vendor states this is fixed in 4479db143390bdcadc1561292aab579cdfa9f6c6 (fixed)
Vendor states this is fixed in a2182743a8b4969481f64aec4908ff162e8a206c (fixed)
Vendor states this is fixed in b8ced2b9a23a1a2c1e0ed8d0d02512e51bdf38da (fixed)
Affected range stops below 6.12, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.35 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.15.4 (unaffected)
Vendor states this is fixed in 6.16 (unaffected)
Vendor states this is fixed in 6.6.95 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/43f26094d6702e494e800532c3f1606e7a68eb30
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4479db143390bdcadc1561292aab579cdfa9f6c6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a2182743a8b4969481f64aec4908ff162e8a206c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b8ced2b9a23a1a2c1e0ed8d0d02512e51bdf38da

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card