PT-2026-151534
CVE-2026-99353
·
Publicado
2026-11-19
·
Atualizado
2026-11-19
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:
SUNRPC: Reject a socket that already has an svc sock attached
Writing the same socket descriptor to /proc/fs/nfsd/portlist twice
attaches a second svc sock to one socket. svc setup socket() saves
the socket's callbacks before installing its own, so the second
attach records svc write space() as the old write space callback.
svc udp init() invokes that callback by way of svc sock setbufsize(),
and svc write space() then calls itself until the kernel stack is
exhausted:
BUG: TASK stack guard page was hit at ffffc900037d7ff8
svc write space+0x90/0x2b0 net/sunrpc/svcsock.c:429
svc write space+0xe6/0x2b0 net/sunrpc/svcsock.c:430
... 700 more ...
svc sock setbufsize+0x18d/0x220 net/sunrpc/svcsock.c:386
svc udp init net/sunrpc/svcsock.c:854 [inline]
svc setup socket+0xb2f/0x1090 net/sunrpc/svcsock.c:1498
svc addsock+0x2fd/0x760 net/sunrpc/svcsock.c:1547
write ports addfd fs/nfsd/nfsctl.c:742 [inline]
write ports+0xa5b/0xcc0 fs/nfsd/nfsctl.c:861
nfsctl transaction write+0x106/0x1a0 fs/nfsd/nfsctl.c:112
svc data ready() and svc tcp state change() chain through their saved
callbacks the same way, so a TCP descriptor added twice recurses on
the next incoming segment instead. Reaching any of this takes a
writer on portlist, and the nfsd filesystem sets no FS USERNS MOUNT,
so the reproducer needs CAP SYS ADMIN in the initial user namespace.
Reject a socket that already carries sk user data. svc setup socket()
overwrites that field unconditionally, so a socket some other
consumer has claimed is one NFSD would corrupt whether or not the
callbacks recurse.
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾