{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-99556","id":"CVE-2026-99556","title":"Linux kernel directory state corruption in ksmbd readdir handling","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: serialize directory emptiness checks with readdir\n\nSMB2 QUERY_DIRECTORY holds fp->readdir_lock while it calls iterate_dir()\non fp->filp. An SMB2 SET_INFO request with FILE_DISPOSITION_INFORMATION\ncan resolve the same FileId and call ksmbd_vfs_empty_dir() on the same\nfilp without that lock.\n\niterate_dir()'s inode read lock ","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: serialize directory emptiness checks with readdir\n\nSMB2 QUERY_DIRECTORY holds fp->readdir_lock while it calls iterate_dir()\non fp->filp. An SMB2 SET_INFO request with FILE_DISPOSITION_INFORMATION\ncan resolve the same FileId and call ksmbd_vfs_empty_dir() on the same\nfilp without that lock.\n\niterate_dir()'s inode read lock permits concurrent readers and does not\nserialize per-file iterator state. ext4 stores its dx readdir cursor and\nfname RB tree in file->private_data. Concurrent reset or refill can\ntherefore free a fname node while the other worker still traverses it or\nretains its RB-tree link, resulting in use-after-free accesses.\n\nAn authenticated SMB client with list and delete rights on a directory in\na writable KSMBD share backed by ext4 can trigger this when the directory\ntakes the dx readdir path. The client overlaps an SMB2 QUERY_DIRECTORY\nrequest with an SMB2 SET_INFO request carrying FILE_DISPOSITION_INFORMATION\non one live FileId.\n\nIn one x86_64 SMP KASAN multi-shot guest using ksmbd-for-next at\n171df27077fb, the unmodified kernel reported a cross-worker use-after-free\nbefore a panic. The first report's access and free stacks show the two\nrequest paths directly (trimmed):\n\n  BUG: KASAN: slab-use-after-free in ext4_htree_store_dirent+0x488/0x550\n  Read of size 8 by task kworker/2:0/29\n  Workqueue: ksmbd-io handle_ksmbd_work\n  Call Trace:\n   ext4_htree_store_dirent+0x488/0x550\n   htree_dirblock_to_tree+0x535/0x990\n   ext4_htree_fill_tree+0x319/0xba0\n   ext4_readdir+0x175a/0x2f40\n   iterate_dir+0x1b6/0x630\n   smb2_query_dir+0x1003/0x1cc0\n\n  Freed by task 279:\n   free_rb_tree_fname+0x67/0xc0\n   ext4_readdir+0x13a9/0x2f40\n   iterate_dir+0x1b6/0x630\n   ksmbd_vfs_empty_dir+0xa2/0x100\n   smb2_set_info+0x2ffa/0x45d0\n\nTake fp->readdir_lock across the entire emptiness check. This places both\niterators over that handle's filp in the same lock domain while\npreserving the disposition status handling. The exact code change\ncompleted a warning-free x86_64 KASAN bzImage build. Tracing three request\npairs showed that the two iterate_dir() calls no longer overlapped and the\nexpected statuses were preserved. A further 1,600 reproducer iterations\ncompleted with expected statuses and no KASAN report, Oops, or panic.\n\nThe reproducer and complete guest configuration are available privately\nto maintainers on request.","published":"2026-11-19T14:45:27.822Z","updated":"2026-11-19T17:00:38.056782078Z","reserved":"2026-09-25T10:25:14.421Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","lessThan":"5ad61a34963f32fc1637d26e88cf6e02a3b99d08","status":"affected","versionType":"git"},{"version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","lessThan":"818a9fd779443b931b05c025d85f29680efb26c2","status":"affected","versionType":"git"},{"version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","lessThan":"2a4b6ae380a9f5175f002c1921cf9cbc7ca536ba","status":"affected","versionType":"git"},{"version":"e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9","lessThan":"7220980b2423d06a0604516129bfa4cec8a697ae","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"5.15","status":"affected"},{"version":"0","lessThan":"5.15","status":"unaffected","versionType":"semver"},{"version":"6.12.117","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.61","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.3.2","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/5ad61a34963f32fc1637d26e88cf6e02a3b99d08","tags":["web"]},{"url":"https://git.kernel.org/stable/c/818a9fd779443b931b05c025d85f29680efb26c2","tags":["web"]},{"url":"https://git.kernel.org/stable/c/2a4b6ae380a9f5175f002c1921cf9cbc7ca536ba","tags":["web"]},{"url":"https://git.kernel.org/stable/c/7220980b2423d06a0604516129bfa4cec8a697ae","tags":["web"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99556.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99556","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":null,"epssPercentile":null,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-99556","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99556","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-99556","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-99556","ok":false,"note":"no score yet"}],"aiTitle":true,"tech":[],"critical":[],"attention":null}