CVE-2026-89710 — NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path
In the Linux kernel, the following vulnerability has been resolved: NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path When the server returns a new layout stateid while a valid one is still held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on the on-stack free_me list and jumps to out_forget. Segments whose reference count drops to zero are unlinked from lo->plh_segs and moved to free_me by mark_lseg_invalid(); for an idle cached segment the layout header holds the only reference, so this happens on the first decrement. out_forget never drains free_me -- only the success path calls pnfs_free_lseg_list(). Commit 814b84971388 ("pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()") added the drain; commit 08bd8dbe8882 ("pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()") removed it while switching the destination to lo->plh_return_segs, which is drained elsewhere. Commit fb700ef02676 ("NFSv4.1: Simplify layout return in pnfs_layout_process()") switched the destination back to free_me without restoring the drain. Restore the pnfs_free_lseg_list() call.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ fb700ef026766c95578aafc0db1b208946e7ad4f and < f52188118d319b47d49ee91a897f6afda4879c59≥ fb700ef026766c95578aafc0db1b208946e7ad4f and < ad3e41855325e55623276660ef20fbc3b8ba087f≥ fb700ef026766c95578aafc0db1b208946e7ad4f and < a080bb69d30f11738d753a60d1eb733d627c2093≥ fb700ef026766c95578aafc0db1b208946e7ad4f and < 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2≥ fb700ef026766c95578aafc0db1b208946e7ad4f and < 36e3f13bf0728f4ce11ee8904cec82a783222f62≥ fb700ef026766c95578aafc0db1b208946e7ad4f and < 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070≥ fb700ef026766c95578aafc0db1b208946e7ad4f and < ee5a386cfe60f3f8286de16a9db8e1a08f0bc124version 5.13 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 20, 2026 · 5 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/ad3e41855325e55623276660ef20fbc3b8ba087f
- nvd.nist.gov/vuln/detail/CVE-2026-89710
- git.kernel.org/stable/c/ee5a386cfe60f3f8286de16a9db8e1a08f0bc124
- git.kernel.org/stable/c/36e3f13bf0728f4ce11ee8904cec82a783222f62
- git.kernel.org/stable/c/a080bb69d30f11738d753a60d1eb733d627c2093
- git.kernel.org/stable/c/32ac1b0b7f1cfa0d1a1faf9c72f4154046101070
- git.kernel.org/stable/c/7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2
- git.kernel.org/stable/c/f52188118d319b47d49ee91a897f6afda4879c59
- github.com/advisories/GHSA-84pc-7mxq-h2j8
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98869 bpf: Infer zext_dst based on static register liveness analysis 1h
- Unknown CVE-2023-7356 Bluetooth: ISO: Copy BASE if service data matches EIR_BAA_SERVICE_UUID 1h
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 3d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 3d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 3d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-89710 is "NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.