CVE-2026-99369: NFSD: Destroy a recalled delegation the client does not hold
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Destroy a recalled delegation the client does not hold
A client that answers CBRECALL with NFS4ERRBADHANDLE or NFS4ERRBADSTATEID has no record of the delegation, so the FREESTATEID that clears it from clrevoked never arrives. Every later SEQUENCE reply carries SEQ4STATUSRECALLABLESTATEREVOKED, and the client loops issuing TESTSTATEID.
Destroy such a delegation when it is reaped rather than revoking it onto clrevoked. RFC 8881 Section 20.2.4 completes the recall at the reply when its status is neither NFS4OK nor NFS4ERRDELAY, so a rejected recall leaves nothing to revoke. An administrative revoke keeps that path, since NFS4ERRADMINREVOKED reports it. A destroyed stateid returns NFS4ERRBADSTATEID instead of NFS4ERRDELEGREVOKED. A client that rejects the recall but still holds the delegation gets no notice that its state was revoked.
CBRECALL can outrun the reply that granted the delegation, so honor a rejection only once the client has seen that grant. Per RFC 8881 Section 2.10.6.3, retirement of the slot that carried the grant is that proof; retry until then, and revoke when the retries lapse.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.3.3-1 - Compensating control
In NFSD, destroy a recalled delegation the client does not hold when it is reaped, rather than revoking it.