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-89694nfsd: check client ownership when cancelling a copy-notify stateid

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: check client ownership when cancelling a copy-notify stateid On the OFFLOAD_CANCEL path (clp != NULL), manage_cpntf_state() freed the target cpntf state without checking ownership. The lookup key st->si_opaque.so_id is allocated cyclically (guessable) and the embedded clientid is the fixed per-net nn->s2s_cp_cl_id, so any authenticated NFSv4.2 client could cancel and free another client's copy-notify stateid. Compare the creating clientid recorded in state->cp_p_clid against the requesting client's cl_clientid and return nfserr_bad_stateid on a mismatch instead of freeing the entry.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < 88daaed26e17e1c7e851859b5bbb4f0e1ab6d0e9
    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < 81b2cfe767943922eca906a2a5af23a0ce5d0f35
    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < 6bba72b8ee68ad631b94bd439592cba46de54d7d
    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < 75268f6cfe26b09a7e4d3216367e87fe9e2a26aa
    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < b1eca07303594ca27f5dc360a6946bd7e1f5b04c
    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < b42dc26a14b4ad5d6daaada11ec4c70744141c25
    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < d801906165cb5cc250d5cbe44935594e170be3e2
    • affected ce0887ac96d35c7105090e166bb0807dc0a0e838 – < 6bdbfab96e0cf25e5f57dac5c09dc1749751a4bf
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .