CVE-2026-89694: nfsd: check client ownership when cancelling a copy-notify stateid
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 6bba72b8ee68ad631b94bd439592cba46de54d7d, 6bdbfab96e0cf25e5f57dac5c09dc1749751a4bf, 75268f6cfe26b09a7e4d3216367e87fe9e2a26aa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 6bba72b8ee68ad631b94bd439592cba46de54d7d, 6bdbfab96e0cf25e5f57dac5c09dc1749751a4bf, 75268f6cfe26b09a7e4d3216367e87fe9e2a26aa; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.6affected
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before 88daaed26e17e1c7e851859b5bbb4f0e1ab6d0e9affected · git
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before 81b2cfe767943922eca906a2a5af23a0ce5d0f35affected · git
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before 6bba72b8ee68ad631b94bd439592cba46de54d7daffected · git
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before 75268f6cfe26b09a7e4d3216367e87fe9e2a26aaaffected · git
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before b1eca07303594ca27f5dc360a6946bd7e1f5b04caffected · git
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before b42dc26a14b4ad5d6daaada11ec4c70744141c25affected · git
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before d801906165cb5cc250d5cbe44935594e170be3e2affected · git
- ce0887ac96d35c7105090e166bb0807dc0a0e838 and later · before 6bdbfab96e0cf25e5f57dac5c09dc1749751a4bfaffected · git
- before 5.6not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89692Sep 11, 2026 · nfsd: clear CALLBACK_RUNNING on failed delegation recall queue30Monitor
- ← EarlierCVE-2026-89693Sep 11, 2026 · nfsd: check nfsd4_acl_to_attr() return value in nfsd4_create()0Monitor
- Later →CVE-2026-89695Sep 11, 2026 · nfsd: cap decoded POSIX ACL count to bound sort cost30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 6bba72b8ee68ad631b94bd439592cba46de54d7d | Vendor (CNA) |
| Linux Linux | 6bdbfab96e0cf25e5f57dac5c09dc1749751a4bf | Vendor (CNA) |
| Linux Linux | 75268f6cfe26b09a7e4d3216367e87fe9e2a26aa | Vendor (CNA) |
| Linux Linux | 81b2cfe767943922eca906a2a5af23a0ce5d0f35 | Vendor (CNA) |
| Linux Linux | 88daaed26e17e1c7e851859b5bbb4f0e1ab6d0e9 | Vendor (CNA) |
| Linux Linux | b1eca07303594ca27f5dc360a6946bd7e1f5b04c | Vendor (CNA) |
| Linux Linux | b42dc26a14b4ad5d6daaada11ec4c70744141c25 | Vendor (CNA) |
| Linux Linux | d801906165cb5cc250d5cbe44935594e170be3e2 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6bdbfab96e0cf25e5f57dac5c09dc1749751a4bf
- git.kernel.org/stable/c/75268f6cfe26b09a7e4d3216367e87fe9e2a26aa
- git.kernel.org/stable/c/81b2cfe767943922eca906a2a5af23a0ce5d0f35
- git.kernel.org/stable/c/88daaed26e17e1c7e851859b5bbb4f0e1ab6d0e9
- git.kernel.org/stable/c/b1eca07303594ca27f5dc360a6946bd7e1f5b04c
- git.kernel.org/stable/c/b42dc26a14b4ad5d6daaada11ec4c70744141c25
- git.kernel.org/stable/c/d801906165cb5cc250d5cbe44935594e170be3e2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.