CVE-2026-90037
Last modified
CVE-2026-90037 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 0.46% chance of exploitation in the next 30 days.
Description
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 217526e7ecc9f6f243e976772e81eab7ab986a4c, < 0763482227822f7343557f086afc382086d56c4c; >= 217526e7ecc9f6f243e976772e81eab7ab986a4c, < 83dd59ac1c3455c2c7d8ddb582d980a13199b9b3; >= 217526e7ecc9f6f243e976772e81eab7ab986a4c, < e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1; >= 217526e7ecc9f6f243e976772e81eab7ab986a4c, < 2330b788d732f43668b965b3105b37ceb276dfea |
| Linux | Linux | 3.17 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90037?
How severe is CVE-2026-90037?
How do I fix CVE-2026-90037?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90031In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90032In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90033In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90034In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90035In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90036In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-90038In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-90039In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90040In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90041In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-90042In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-90043In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-90037?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
