Skip to main content

Linux Kernel CVE-2026-64108

| EUVDEUVD-2026-45793 HIGH
2026-07-19 Linux GHSA-3mrw-xf65-fqjh
7.8
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.3 MEDIUM

Local mount/unmount access needed (AV:L, PR:L) and success depends on winning an async worker/unmount race (AC:H); realistic impact is DoS/instability (A:H, I:L) rather than confidentiality loss (C:N).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jul 20, 2026 - 17:29 vuln.today
CVSS changed
Jul 20, 2026 - 15:22 NVD
7.8 (HIGH)
Patch available
Jul 19, 2026 - 17:03 EUVD
CVE Published
Jul 19, 2026 - 15:40 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 19, 2026 - 15:40 cve.org
HIGH 7.8

DescriptionCVE.org

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.

AnalysisAI

Use-after-free / dangling dentry reference in the Linux kernel's CIFS (SMB) client allows a local user to leave a filesystem dentry in use after unmount, triggering a 'still in use' warning and potential memory corruption. Introduced by commit 340cea84f691c ('cifs: open files should not hold ref on superblock'), the flaw affects multiple stable series (6.1.x, 6.6.x, 6.12.x, 6.18.x, 6.19.x, 7.0.x) where a deferred CIFS close work item can run after the superblock is torn down. No public exploit has been identified, though a crash reproducer is published in the kernel bugzilla, and EPSS is low (0.17%, 7th percentile) with no CISA KEV listing.

Technical ContextAI

The bug lives in the CIFS/SMB client filesystem (fs/smb/client) of the Linux kernel. CIFS supports 'deferred close', where closing a file queues delayed work (cfile->deferred on deferredclose_wq) instead of immediately releasing the handle, and each open cifsFileInfo holds only a dentry reference (dget) rather than a superblock reference after commit 340cea84f691c. The root-cause class is a use-after-free / lifetime ordering error (CWE-416-style, though NVD lists CWE as N/A): during unmount, cifs_kill_sb() calls cifs_close_all_deferred_files_sb() but the deferred close worker may already have removed the cfile from the per-superblock list, so the cleanup path skips it. kill_anon_super() → generic_shutdown_super() → shrink_dcache_for_umount() then finds the dentry with d_lockref.count still at 1 and warns, after which the deferred worker's cifsFileInfo_put_final()/dput() drops the reference on already-freed/torn-down structures. The fix flushes deferredclose_wq before calling kill_anon_super() so all pending closes complete first. CPE data identifies the affected component only generically as cpe:2.3:a:linux:linux (the kernel itself).

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 6.1.175, 6.6.142, 6.12.92, 6.18.34, 7.0.11, or 7.1 (or later) depending on your series; the fix commits are published at git.kernel.org (e.g. c7364cea52531534676b9f7dbc0a477c11f4c050 and the sibling backports bdc349a87f1f, f2deaa2f409a, 5e7d9d0805e5, e1ffa6cf6623, c68337442f03). If immediate patching is not possible, the practical compensating control is to avoid the trigger: restrict or disable CIFS/SMB mounts on affected hosts, and prevent unprivileged users from mounting CIFS shares (avoid granting CAP_SYS_ADMIN / user-namespace mount rights and audit fstab/autofs entries) so untrusted local users cannot drive the open-close-unmount sequence - the trade-off is loss of SMB share access for those workflows. Because the trigger involves deferred close plus unmount, avoiding frequent programmatic mount/unmount cycles of CIFS filesystems reduces exposure until patched. Track the advisory at https://nvd.nist.gov/vuln/detail/CVE-2026-64108.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-64108 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy