CVE-2026-99540
ksmbd: fix parent dentry lifetime in directory enumeration
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9; < 32934b13b1a63c86d2fa68df0bfb28c51ce38879 (affected, git) ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9; < 93566781118cdff874023d5ca4e7b8054baaec31 (affected, git) ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9; < b62ef8cfec9351662e42cbf7da2d743068699bba (affected, git) ≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9; < 171df27077fb49b4af2c53ad2cedcd0e39664fe8 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
5.15 (affected) ≥ 0; < 5.15 (unaffected, semver) ≥ 6.12.117; ≤ 6.12.* (unaffected, semver) ≥ 6.18.61; ≤ 6.18.* (unaffected, semver) ≥ 7.3.2; ≤ 7.3.* (unaffected, semver) ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 8.8 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA: Linux |
| 3.1 / 8.8 high |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/32934b13b1a63c86d2fa68df0bfb28c51ce38879CNA: Linux
- https://git.kernel.org/stable/c/93566781118cdff874023d5ca4e7b8054baaec31CNA: Linux
- https://git.kernel.org/stable/c/b62ef8cfec9351662e42cbf7da2d743068699bbaCNA: Linux
- https://git.kernel.org/stable/c/171df27077fb49b4af2c53ad2cedcd0e39664fe8CNA: Linux
- https://git.kernel.org/stable/c/171df27077fb49b4af2c53ad2cedcd0e39664fe8416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/32934b13b1a63c86d2fa68df0bfb28c51ce38879416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/93566781118cdff874023d5ca4e7b8054baaec31416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/b62ef8cfec9351662e42cbf7da2d743068699bba416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.