BaselineWatch
Desk

CVE-2026-90037

9.8 critical Published

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.

Fix

Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.

Change history 5

  1. StatusReceived → PublishedNVD modified 2026-10-21 12:49
  2. References+1 references (now 5)NVD modified 2026-10-21 13:20
  3. StatusPublished → ReceivedNVD modified 2026-10-21 13:20
  4. StatusReceived → PublishedNVD modified 2026-10-19 08:56
  5. First seenCVSS 9.8NVD modified 2026-10-19 09:18

Affected (CPE criteria) 0

NVD has not attached CPE configurations yet.

References 5