PT-2026-151543
CVE-2026-99362
·
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:
nfsd: preflight SEQUENCE replies before accepting a slot
nfsd4 sequence() narrows the reply buffer to the session's cached
reply limit before it accepts the slot seqid. A client may negotiate
ca maxresponsesize cached down to NFSD MIN HDR SEQ SZ, and
nfsd4 alloc slot() then gives every slot a zero-length sl data[]. A
COMPOUND tag can fill that narrowed buffer until it holds the
SEQUENCE opcode but not the status word that follows.
nfsd4 encode operation() returns without running
nfsd4 encode sequence(), so cstate.data offset stays zero. It leaves
op->status at nfs ok as well, so the COMPOUND is treated as having
succeeded.
nfsd4 store cache entry() declines to cache a lone SEQUENCE that
returned an error. That test reads the status the operation
reported, so it passes here. The copy starts at offset zero and
takes the whole reply, RPC and COMPOUND headers included, into the
zero-length sl data[]. The COMPOUND tag is copied along with it, so
the client picks most of the bytes written past the end of the slot:
BUG: KASAN: slab-out-of-bounds in read bytes from xdr buf+0x1bc/0x390
Write of size 80 at addr ffff888003a549cd by task kunit try catch/24
asan memcpy+0x38/0x60
read bytes from xdr buf+0x1bc/0x390
nfsd4 sequence done+0x5b0/0x810
nfs4svc encode compoundres+0x1bf/0x240
Check that the fixed-size SEQUENCE result, plus room for a following
operation's error status, fits the negotiated limit before narrowing
the buffer and consuming the slot seqid. The slot and its reply
cache are left unchanged, as RFC 8881 Section 2.10.6.1.2 requires of
an error returned from SEQUENCE.
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾