CVE-2026-90037
CVE CVE-2026-90037EUVD EUVD-2026-80645Published 2026-09-16T10:33:36.000ZLast changed 2026-09-21T13:15:13.000ZCVSS 9.8
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; 217526e7ecc9f6f243e976772e81eab7ab986a4c <2330b788d732f43668b965b3105b37ceb276dfea; 217526e7ecc9f6f243e976772e81eab7ab986a4c <e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1; 3.17; 217526e7ecc9f6f243e976772e81eab7ab986a4c <0763482227822f7343557f086afc382086d56c4c; patch: 7.2.5; patch: 6.12.111; patch: 7.3-rc1; 217526e7ecc9f6f243e976772e81eab7ab986a4c <83dd59ac1c3455c2c7d8ddb582d980a13199b9b3; patch: 6.18.51
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.