PT-2026-151547

CVE-2026-99366

·

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:
nfsd: don't modify a session slot when replaying its cached reply
nfsd4 sequence() claims a session slot by setting NFSD4 SLOT INUSE under nn->client lock. A reply served from the slot's reply cache does not claim it, and that distinction lived only in cstate->status, which nfsd4 sequence() set to nfserr replay cache. Commit cc028a10a48c ("NFSD: Hoist status code encoding into XDR encoder functions") moved nfsd4 proc compound()'s cstate->status assignment below the out: label, and the replay path's goto out was the one path that relied on skipping it. The test in nfsd4 sequence done() therefore no longer identifies a replay, and every replay now stores its reply and clears NFSD4 SLOT INUSE as though it owned the slot.
NFSD4 SLOT INUSE is the interlock: check slot seqid() rejects every sequence id for a slot that is in use, before replay matches cache() runs. A replay never sets it, so two replays can be in flight on the same slot at once. One can read slot->sl cred under nn->client lock while the other's completion frees and rebuilds it from the XDR encoder without that lock. Two completions can also collide with each other and release the same group info twice. free svc cred() leaves cr uid, cr gid and cr flavor intact, so the reader passes every earlier test in same creds() and dereferences a NULL cr group info. From a 6.12.91 production server:
BUG: kernel NULL pointer dereference, address: 0000000000000004 CPU: 63 UID: 0 PID: 39015 Comm: nfsd RIP: 0010:same creds+0x38/0xa0 [nfsd] RDX: 0000000000000000 Call Trace: nfsd4 sequence+0x6a8/0x910 [nfsd] nfsd4 proc compound+0x345/0x670 [nfsd] nfsd dispatch+0x100/0x220 [nfsd] svc process common+0x311/0x700 [sunrpc] svc process+0x131/0x1c0 [sunrpc] svc recv+0x7ef/0x9c0 [sunrpc] nfsd+0xa3/0x100 [nfsd] Kernel panic - not syncing: Fatal exception
Since v6.14 a live session's slot table can shrink, and the unowned store becomes a use-after-free write. nfsd4 sequence() defers the shrink while a slot is in use, but it tests NFSD4 SLOT INUSE, which a replay does not set, so free session slots() can kfree() the slot the replay still holds in cstate->slot.
Record the claim in cstate->slot owned when nfsd4 sequence() accepts a request and test that in nfsd4 sequence done(), so only the request that claimed the slot updates its cached reply and clears NFSD4 SLOT INUSE. svc generic init request() zeroes the compound response before each request, so the flag starts clear.
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾