{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99556","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.421Z","datePublished":"2026-11-19T14:45:27.822Z","dateUpdated":"2026-11-22T11:08:55.938Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-22T11:08:55.938Z"},"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":8.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:N - SMB2 SET_INFO with FileInfoClass FILE_DISPOSITION_INFORMATION and DeletePending is the request that reaches set_file_disposition_info: ksmbd_tcp_read feeds ksmbd_conn_handler_loop, which queues handle_ksmbd_work and dispatches smb2_set_info. The overlapping SMB2 QUERY_DIRECTORY on that same VolatileFileId is the other half of the race.\nAC:L - The client opens one directory FileId and sends both SMB2 requests; ksmbd_conn_handler_loop queues each PDU to a separate ksmbd-io worker while credits remain, so both sides of the race are the client's. Creating a one-block directory on the ext4 share makes is_dx_dir true and selects ext4_dx_readdir, which is the state the client needs.\nPR:L - smb2_check_user_session runs before the command table and accepts SMB2 QUERY_DIRECTORY and SMB2 SET_INFO only for a SMB2_SESSION_VALID SessionId. set_file_disposition_info additionally requires fp->daccess FILE_DELETE_LE, smb2_query_dir requires FILE_LIST_DIRECTORY_LE, and smb2_set_info requires KSMBD_TREE_CONN_FLAG_WRITABLE.\nUI:N - The authenticated client issues SMB2 CREATE for the directory and then the overlapping QUERY_DIRECTORY and SET_INFO on the returned FileId. Exploitation uses only that client's own requests.\nS:U - set_file_disposition_info and ext4_dx_readdir both run in the host kernel's ksmbd-io worker, and the corrupted fname slab objects are host kernel memory. The impact remains inside that kernel security authority.\nC:H - free_rb_tree_fname, called from ext4_dx_readdir during ksmbd_vfs_empty_dir, kfree's the fname nodes in file->private_data while ext4_htree_store_dirent on the query-directory worker still reads fname->hash and the rb_left/rb_right links. Reclaiming that kmalloc slot with chosen filename-sized objects turns the walk into a kernel read.\nI:H - ext4_htree_store_dirent writes fname->next on a hash match and rb_link_node stores the new node through the parent's rb_left or rb_right. Those fields belong to the fname that free_rb_tree_fname already freed, so a reclaimed slab becomes a kernel write through the attacker's replacement bytes.\nA:H - The KASAN report is a slab use-after-free in ext4_htree_store_dirent on the ksmbd-io workqueue, with the free stack in ksmbd_vfs_empty_dir, and the unmodified kernel panicked. A fault on the freed rb node oopses the host from either worker."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c"],"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"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/smb/server/smb2pdu.c"],"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"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"6.12.117"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"6.18.61"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"7.3.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"7.4-rc1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/5ad61a34963f32fc1637d26e88cf6e02a3b99d08"},{"url":"https://git.kernel.org/stable/c/818a9fd779443b931b05c025d85f29680efb26c2"},{"url":"https://git.kernel.org/stable/c/2a4b6ae380a9f5175f002c1921cf9cbc7ca536ba"},{"url":"https://git.kernel.org/stable/c/7220980b2423d06a0604516129bfa4cec8a697ae"}],"title":"ksmbd: serialize directory emptiness checks with readdir","x_generator":{"engine":"bippy-1.2.0"}}}}