PT-2026-151550
CVE-2026-99369
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Destroy a recalled delegation the client does not hold
A client that answers CB RECALL with NFS4ERR BADHANDLE or
NFS4ERR BAD STATEID has no record of the delegation, so the
FREE STATEID that clears it from cl revoked never arrives. Every later
SEQUENCE reply carries SEQ4 STATUS RECALLABLE STATE REVOKED, and the
client loops issuing TEST STATEID.
Destroy such a delegation when it is reaped rather than revoking it
onto cl revoked. RFC 8881 Section 20.2.4 completes the recall at the
reply when its status is neither NFS4 OK nor NFS4ERR DELAY, so a
rejected recall leaves nothing to revoke. An administrative revoke
keeps that path, since NFS4ERR ADMIN REVOKED reports it. A destroyed
stateid returns NFS4ERR BAD STATEID instead of NFS4ERR DELEG REVOKED. A
client that rejects the recall but still holds the delegation gets no
notice that its state was revoked.
CB RECALL 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.
Found an issue in the description? Have something to add? Feel free to write us 👾