PT-2026-151751

CVE-2026-99540

·

Published

2026-11-19

·

Updated

2026-11-19

Description by

Score
N/A
Not available

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.

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.
Vendors
Affected products
Related identifiers
Found an issue in the description? Have something to add? Feel free to write us 👾