Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90037NFSD: Prevent client use-after-free during close_lru reaping

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-90037, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.51% · top 56% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 217526e7ecc9f6f243e976772e81eab7ab986a4c – < 1d721729762a413015864b2a56d7fb86fb8efa9f
    • affected 217526e7ecc9f6f243e976772e81eab7ab986a4c – < adc34b5df5c5d87043cb500b0867fc1c4ad0117e
    • affected 217526e7ecc9f6f243e976772e81eab7ab986a4c – < 0763482227822f7343557f086afc382086d56c4c
    • affected 217526e7ecc9f6f243e976772e81eab7ab986a4c – < 83dd59ac1c3455c2c7d8ddb582d980a13199b9b3
    • affected 217526e7ecc9f6f243e976772e81eab7ab986a4c – < e57a9ed34ea8c17e831de59b8f1a6b2d80d347a1
    • affected 217526e7ecc9f6f243e976772e81eab7ab986a4c – < 2330b788d732f43668b965b3105b37ceb276dfea
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90037 badge
[![CVE-2026-90037](https://cveledger.app/badge/CVE-2026-90037.svg)](https://cveledger.app/cve/CVE-2026-90037)

Record last updated .