PT-2026-151767

CVE-2026-99556

·

Publicado

2026-11-19

·

Atualizado

2026-11-19

Descrição por

Pontuação
N/A
Não disponível

Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.

In the Linux kernel, the following vulnerability has been resolved:
ksmbd: serialize directory emptiness checks with readdir
SMB2 QUERY DIRECTORY holds fp->readdir lock while it calls iterate dir() on fp->filp. An SMB2 SET INFO request with FILE DISPOSITION INFORMATION can resolve the same FileId and call ksmbd vfs empty dir() on the same filp without that lock.
iterate dir()'s inode read lock permits concurrent readers and does not serialize per-file iterator state. ext4 stores its dx readdir cursor and fname RB tree in file->private data. Concurrent reset or refill can therefore free a fname node while the other worker still traverses it or retains its RB-tree link, resulting in use-after-free accesses.
An authenticated SMB client with list and delete rights on a directory in a writable KSMBD share backed by ext4 can trigger this when the directory takes the dx readdir path. The client overlaps an SMB2 QUERY DIRECTORY request with an SMB2 SET INFO request carrying FILE DISPOSITION INFORMATION on one live FileId.
In one x86 64 SMP KASAN multi-shot guest using ksmbd-for-next at 171df27077fb, the unmodified kernel reported a cross-worker use-after-free before a panic. The first report's access and free stacks show the two request paths directly (trimmed):
BUG: KASAN: slab-use-after-free in ext4 htree store dirent+0x488/0x550 Read of size 8 by task kworker/2:0/29 Workqueue: ksmbd-io handle ksmbd work Call Trace: ext4 htree store dirent+0x488/0x550 htree dirblock to tree+0x535/0x990 ext4 htree fill tree+0x319/0xba0 ext4 readdir+0x175a/0x2f40 iterate dir+0x1b6/0x630 smb2 query dir+0x1003/0x1cc0
Freed by task 279: free rb tree fname+0x67/0xc0 ext4 readdir+0x13a9/0x2f40 iterate dir+0x1b6/0x630 ksmbd vfs empty dir+0xa2/0x100 smb2 set info+0x2ffa/0x45d0
Take fp->readdir lock across the entire emptiness check. This places both iterators over that handle's filp in the same lock domain while preserving the disposition status handling. The exact code change completed a warning-free x86 64 KASAN bzImage build. Tracing three request pairs showed that the two iterate dir() calls no longer overlapped and the expected statuses were preserved. A further 1,600 reproducer iterations completed with expected statuses and no KASAN report, Oops, or panic.
The reproducer and complete guest configuration are available privately to maintainers on request.
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾