nfsd: set SC_STATUS_FREED in nfsd4_drop_revoked_stid for delegations
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nfsd: set SC_STATUS_FREED in nfsd4_drop_revoked_stid for delegations
nfsd4_drop_revoked_stid() handles FREE_STATEID for admin-revoked delegations but does not set SC_STATUS_FREED before releasing cl_lock. revoke_delegation() uses this flag to detect whether FREE_STATEID has already processed the delegation -- without it, the freed delegation is added to cl_revoked via list_add(), producing a use-after-free when cl_revoked is later traversed in __destroy_client().
The SC_STATUS_REVOKED path in nfsd4_free_stateid() (line 7983) already sets SC_STATUS_FREED correctly. Apply the same pattern to the SC_STATUS_ADMIN_REVOKED path in nfsd4_drop_revoked_stid().
From the CVE record · Linux
In the Linux kernel's nfsd, FREE_STATEID processing for an admin-revoked delegation can leave a freed delegation on the revoked list. An attacker who can trigger this processing may cause a use-after-free when that list is later traversed; the input does not establish the required access, authentication, or user interaction.
Engineers running Linux kernels with nfsd should check their versions; affected versions are not specified in the input.