NFSD: Destroy a recalled delegation the client does not hold
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel bbfa823f624d41e85ebca929ac77dc2182cadfed, Kernel d568594503a09ed2761fada2117e4fbaa31972e0 and Kernel 7.3.2.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =3.10, >=3bd64a5ba1719c2bb6cba4493dfd3e23a7653e54 <bbfa823f624d41e85ebca929ac77dc2182cadfed, >=3bd64a5ba1719c2bb6cba4493dfd3e23a7653e54 <d568594503a09ed2761fada2117e4fbaa31972e0 | bbfa823f624d41e85ebca929ac77dc2182cadfed, d568594503a09ed2761fada2117e4fbaa31972e0 |
| linux-kernel: Kernel | >=3.10.0 <7.3.2 | 7.3.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket