PT-2026-148133
CVE-2026-99289
·
Publicado
2026-11-16
·
Atualizado
2026-11-16
Descrição por
Pontuação
N/A
Não disponívelNã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: fix app-instance non-durable supersede session UAF
ksmbd close fd app instance id() supersedes a prior open that has the
same AppInstanceId. It reaches that open's session through opinfo->sess.
This pointer is not refcounted.
Session teardown detaches durable handles before it frees the session.
It does not detach a non-durable open. That open still points at the
session through opinfo->sess after the session is freed. Another session
can supersede the open at the same time. The supersede then takes a
write lock through the stale pointer, in the freed session's file table.
BUG: KASAN: slab-use-after-free in raw write lock+0x71/0xd0
Call Trace:
raw write lock+0x71/0xd0
ksmbd close fd app instance id+0xd9/0x670 [ksmbd]
smb2 open+0x3e10/0xd910 [ksmbd]
Freed by task 212:
ksmbd session destroy+0x38d/0x480 [ksmbd]
Fix this by looking the session up by opinfo->session id. The lookup
returns a reference, as smb2 break collect channels() does. Recheck that
opinfo->sess still points at it before using it.
Do the lookup without m lock held. destroy previous session() takes
m lock under the session table lock, and taking them in the other order
here would deadlock.
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾