NFSD: Prevent client use-after-free during close_lru reaping
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 217526e7ecc9f6f243e976772e81eab7ab986a4c · < 2330b788d732f43668b965b3105b37ceb276dfea| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Prevent client use-after-free during close_lru reaping
An nfs4_openowner left on nn->close_lru after its final CLOSE keeps its last closed stateid in oo_last_closed_stid, holding only a raw pointer to its nfs4_client. The laundromat reaps timed-out entries, drops nn->client_lock, and calls nfs4_put_stid(), which dereferences the client through cl_lock. Nothing pins the client across that window, so a concurrent force_expire_client() can free it and nfs4_put_stid() reads freed memory. __destroy_client() hits the same race, walking clp->cl_openowners without cl_lock.
Pin the client with cl_rpc_users before dropping client_lock, and skip clients already expiring. __destroy_client() then cleans up its own close_lru entries through release_last_closed_stateid(), so teardown no longer races the laundromat.
From the CVE record · Linux
Linux kernel NFSD can read freed client memory when close_lru reaping races with client expiration or destruction. The issue involves an openowner left on close_lru after its final CLOSE; the input does not specify whether exploitation requires network access, authentication, or user interaction.
Operators running Linux kernel NFSD should check their kernel; affected versions are not specified.