CVE-2026-99540

published 19 Nov 2026 · updated 21 Nov 2026

ksmbd: fix parent dentry lifetime in directory enumeration

6.5MediumCVSS 6.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b62ef8cfec9351662e42cbf7da2d743068699bba, Kernel 171df27077fb49b4af2c53ad2cedcd0e39664fe8, Kernel 32934b13b1a63c86d2fa68df0bfb28c51ce38879 and 4 more.

In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix parent dentry lifetime in directory enumeration ksmbd_populate_dot_dotdot_entries() builds the ".." entry from the open directory's d_parent and passes that pointer to ksmbd_vfs_fill_dentry_attrs() without taking a reference. That pointer is only valid while the directory stays under this parent. If a concurrent rename moves the directory elsewhere, the old parent loses its last reference; a following rmdir then turns it into a negative dentry with d_inode cleared, and after the RCU grace period the dentry itself is freed. The worker still holds the raw pointer and dereferences d_inode through vfs_getattr() and vfs_getxattr(). A remote SMB client, authenticated or guest, triggers this by listing a directory while that directory is moved under a new parent and the old parent is deleted. It can be done by the client itself with write access or by other concurrent writers, triggering null-ptr-deref and slab-use-after-free on a KASAN build. KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] Workqueue: ksmbd-io handle_ksmbd_work RIP: 0010:xattr_permission+0x9d/0x160 Call Trace: vfs_getxattr+0x9c/0x1b0 ksmbd_vfs_getxattr+0x82/0x100 ksmbd_vfs_get_dos_attrib_xattr+0x7f/0x130 ksmbd_vfs_fill_dentry_attrs+0x435/0x650 ksmbd_populate_dot_dotdot_entries+0x25e/0x630 smb2_query_dir+0xcf9/0x1a20 handle_ksmbd_work+0x5f1/0x1c80 process_one_work+0x90b/0x19d0 Fix by using the dentry reference counting APIs: take the parent with dget_parent(), take a matching dget() on ".", and dput() the dentry once ksmbd_vfs_fill_dentry_attrs() has returned or the pattern does not match.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <b62ef8cfec9351662e42cbf7da2d743068699bba, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <171df27077fb49b4af2c53ad2cedcd0e39664fe8, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <32934b13b1a63c86d2fa68df0bfb28c51ce38879, >=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <93566781118cdff874023d5ca4e7b8054baaec31, =5.15b62ef8cfec9351662e42cbf7da2d743068699bba, 171df27077fb49b4af2c53ad2cedcd0e39664fe8, 32934b13b1a63c86d2fa68df0bfb28c51ce38879, 93566781118cdff874023d5ca4e7b8054baaec31
linux-kernel: Kernel>=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=5.15.0 <6.12.1176.18.61, 7.3.2, 6.12.117

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99540 severity on Zeptric[![CVE-2026-99540](https://zeptric.io/badge/cve/CVE-2026-99540.svg)](https://zeptric.io/cve/CVE-2026-99540)