NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070, 36e3f13bf0728f4ce11ee8904cec82a783222f62, 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070, 36e3f13bf0728f4ce11ee8904cec82a783222f62, 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2 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: 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.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 6th 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.1%
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.13affected
- fb700ef026766c95578aafc0db1b208946e7ad4f and later · before f52188118d319b47d49ee91a897f6afda4879c59affected · git
- fb700ef026766c95578aafc0db1b208946e7ad4f and later · before ad3e41855325e55623276660ef20fbc3b8ba087faffected · git
- fb700ef026766c95578aafc0db1b208946e7ad4f and later · before a080bb69d30f11738d753a60d1eb733d627c2093affected · git
- fb700ef026766c95578aafc0db1b208946e7ad4f and later · before 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2affected · git
- fb700ef026766c95578aafc0db1b208946e7ad4f and later · before 36e3f13bf0728f4ce11ee8904cec82a783222f62affected · git
- fb700ef026766c95578aafc0db1b208946e7ad4f and later · before 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070affected · git
- fb700ef026766c95578aafc0db1b208946e7ad4f and later · before ee5a386cfe60f3f8286de16a9db8e1a08f0bc124affected · git
- before 5.13not affected · semver
- 5.15.221 and later · up to and including 5.15.*not 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-89708Sep 11, 2026 · nfsd: RCU-protect cl_cb_session to fix use-after-free on session teardown39Monitor
- ← EarlierCVE-2026-89709Sep 11, 2026 · lockd, nfsd: RCU-protect nlmsvc_ops dispatch32Monitor
- Later →CVE-2026-89711Sep 11, 2026 · NFSD: remove flawed WARN_ON_ONCE from nfsd_mode_check32Monitor
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 | 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070 | Vendor (CNA) |
| Linux Linux | 36e3f13bf0728f4ce11ee8904cec82a783222f62 | Vendor (CNA) |
| Linux Linux | 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2 | Vendor (CNA) |
| Linux Linux | a080bb69d30f11738d753a60d1eb733d627c2093 | Vendor (CNA) |
| Linux Linux | ad3e41855325e55623276660ef20fbc3b8ba087f | Vendor (CNA) |
| Linux Linux | ee5a386cfe60f3f8286de16a9db8e1a08f0bc124 | Vendor (CNA) |
| Linux Linux | f52188118d319b47d49ee91a897f6afda4879c59 | Vendor (CNA) |
| 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 (6 more)Show less
- git.kernel.org/stable/c/36e3f13bf0728f4ce11ee8904cec82a783222f62
- git.kernel.org/stable/c/7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2
- git.kernel.org/stable/c/a080bb69d30f11738d753a60d1eb733d627c2093
- git.kernel.org/stable/c/ad3e41855325e55623276660ef20fbc3b8ba087f
- git.kernel.org/stable/c/ee5a386cfe60f3f8286de16a9db8e1a08f0bc124
- git.kernel.org/stable/c/f52188118d319b47d49ee91a897f6afda4879c59
Vendor advisories and official records. Exploit/PoC links are deliberately left out.