CVE-2026-64108

CVE CVE-2026-64108EUVD EUVD-2026-45793Published 2026-07-19T15:40:10.000ZLast changed 2026-08-05T12:39:17.000ZCVSS 7.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 6.18.20 <6.18.34; 7.0; 6.1.167 <6.1.175; 0629a1a187e424373364d681b42b101894bdb548 <bdc349a87f1fb02c18c4071858a06542bfea783d; 340cea84f691c5206561bb2e0147158fe02070be <c68337442f03953237a94577beb468ab2662a851; 30afc6ea72cc6cf7c8d579e79b64232801c38d08; patch: 6.6.142; patch: 6.12.92; patch: 6.1.175; 340cea84f691c5206561bb2e0147158fe02070be <e1ffa6cf662383f95816eed1b623429d82675e75; patch: 7.0.11; patch: 7.1; patch: 0; 708c276f516d27beaded7f372ac8111cee43926c <c7364cea52531534676b9f7dbc0a477c11f4c050; 6.12.78 <6.12.92; 0e4b8faaaebe3137bec5723ef2b3cb0437fb38fd <f2deaa2f409a4598eaa10f2a93a676c0632af248; 6.19.10 <6.20; patch: 6.18.34; 6.6.130 <6.6.142; f655467a9973f964b267871e5fef533ad5014494 <5e7d9d0805e58fa3760894e73115b7a74024fd07

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.