NFSD: Prevent client use-after-free during delegation revoke
Summary
| CVE | CVE-2026-89659 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-11 20:19:52 UTC |
| Updated | 2026-09-11 20:19:52 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
NFSD: Prevent client use-after-free during delegation revoke
A delegation stateid holds only a bare pointer to its owning
nfs4_client and does not keep it alive. The client survives its
stateids only because __destroy_client() drains cl_delegations and
cl_revoked before free_client() runs.
nfs4_laundromat() breaks that invariant: it unhashes an
expired delegation from cl_delegations, drops deleg_lock, then
revoke_delegation() relinks it onto cl_revoked under cl_lock. In that
window the delegation is on neither list, so client_has_state() can
report no remaining state.
Every teardown path first requires cl_rpc_users to be zero, but
the laundromat holds no such reference. A client whose recalled
delegation has just timed out can therefore reach free_client()
while revoke_delegation() is still about to dereference cl_lock,
a use-after-free.
Pin the client with cl_rpc_users across the revoke so teardown blocks
until it completes, then reap the delegation from cl_revoked. A client
already expiring reaps its own, so skip it and leave the delegation on
del_recall_lru. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 3bd64a5ba1719c2bb6cba4493dfd3e23a7653e54 3c0a53ee0b442348d8d2286d6960d3f07bb3a3d3 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3bd64a5ba1719c2bb6cba4493dfd3e23a7653e54 2a9d637c2a8fd8ac29ad9b29f28d122ef75c1a56 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3bd64a5ba1719c2bb6cba4493dfd3e23a7653e54 4683ca76b3b7e5808338491c6eb3c20e6b4894d5 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3.10 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 3.10 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.51 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.4 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/3c0a53ee0b442348d8d2286d6960d3f07bb3a3d3 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/4683ca76b3b7e5808338491c6eb3c20e6b4894d5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2a9d637c2a8fd8ac29ad9b29f28d122ef75c1a56 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.