CVE-2026-64108

cifs: Fix busy dentry used after unmounting

HIGH
7.8
CVSS Score
Published: July 19, 2026 at 03:40 PM UTC
Updated: August 12, 2026 at 03:28 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
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: cifs: Fix busy dentry used after unmounting Since commit 340cea84f691c ("cifs: open files should not hold ref on superblock"), cifs file only holds the dentry ref_cnt, the cifs file close work(cfile->deferred) could be executed after unmounting, which will trigger a warning in generic_shutdown_super: BUG: Dentry 00000000a14a6845{i=c,n=file} still in use (1) [unmount of cifs cifs] The detailed processs is: process A process B kworker fd = open(PATH) vfs_open file->__f_path = *path // dentry->d_lockref.count = 1 cifs_open cifs_new_fileinfo cfile->dentry = dget(dentry) // dentry->d_lockref.count = 2 close(fd) __fput cifs_close queue_delayed_work(deferredclose_wq, cfile->deferred) dput(dentry) // dentry->d_lockref.count = 1 smb2_deferred_work_close _cifsFileInfo_put list_del(&cifs_file->flist) umount cleanup_mnt deactivate_super cifs_kill_sb cifs_close_all_deferred_files_sb cifs_close_all_deferred_files // cannot find cfile, skip _cifsFileInfo_put kill_anon_super generic_shutdown_super shrink_dcache_for_umount umount_check WARN ! // dentry->d_lockref.count = 1 cifsFileInfo_put_final dput(cifs_file->dentry) // dentry->d_lockref.count = 0 Fix it by flushing 'deferredclose_wq' before calling kill_anon_super. Fetch a reproducer in https://bugzilla.kernel.org/show_bug.cgi?id=221548.

Affected

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

v ≥ 6.19.106.1.167 ≤ v < 6.1.1756.12.78 ≤ v < 6.12.926.18.20 ≤ v < 6.18.346.19.10 ≤ v < 6.206.19.10 ≤ v < 7.06.6.130 ≤ v < 6.6.1427.0 ≤ v < 7.0.117.0 ≤ v < 7.17.0.1 ≤ v < 7.0.110e4b8faaaebe3137bec5723ef2b3cb0437fb38fd30afc6ea72cc6cf7c8d579e79b64232801c38d08340cea84f691c5206561bb2e0147158fe02070be6.1.1676.12.786.18.206.19.106.6.130629a1a187e424373364d681b42b101894bdb5487.07.0 rc37.0 rc47.0 rc57.0 rc67.0 rc77.1 rc17.1 rc27.1 rc37.1 rc4708c276f516d27beaded7f372ac8111cee43926cf655467a9973f964b267871e5fef533ad5014494
Vendor states this is fixed in 5e7d9d0805e58fa3760894e73115b7a74024fd07 (fixed)
Vendor states this is fixed in bdc349a87f1fb02c18c4071858a06542bfea783d (fixed)
Vendor states this is fixed in c68337442f03953237a94577beb468ab2662a851 (fixed)
Vendor states this is fixed in c7364cea52531534676b9f7dbc0a477c11f4c050 (fixed)
Vendor states this is fixed in e1ffa6cf662383f95816eed1b623429d82675e75 (fixed)
Vendor states this is fixed in f2deaa2f409a4598eaa10f2a93a676c0632af248 (fixed)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.92 (unaffected)
Vendor states this is fixed in 6.18.34 (unaffected)
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.142 (unaffected)
Vendor states this is fixed in 7.0 (unaffected)
Vendor states this is fixed in 7.0.11 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusANALYZED
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