CVE-2026-89710NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 38 days later
· 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.17% · top 93% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected fb700ef026766c95578aafc0db1b208946e7ad4f – < f52188118d319b47d49ee91a897f6afda4879c59
- affected fb700ef026766c95578aafc0db1b208946e7ad4f – < ad3e41855325e55623276660ef20fbc3b8ba087f
- affected fb700ef026766c95578aafc0db1b208946e7ad4f – < a080bb69d30f11738d753a60d1eb733d627c2093
- affected fb700ef026766c95578aafc0db1b208946e7ad4f – < 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2
- affected fb700ef026766c95578aafc0db1b208946e7ad4f – < 36e3f13bf0728f4ce11ee8904cec82a783222f62
- affected fb700ef026766c95578aafc0db1b208946e7ad4f – < 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070
- affected fb700ef026766c95578aafc0db1b208946e7ad4f – < ee5a386cfe60f3f8286de16a9db8e1a08f0bc124
- affected 5.13
- unaffected < 5.13
- 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
References7
- https://git.kernel.org/stable/c/f52188118d319b47d49ee91a897f6afda4879c59 (opens in a new tab)
- https://git.kernel.org/stable/c/ad3e41855325e55623276660ef20fbc3b8ba087f (opens in a new tab)
- https://git.kernel.org/stable/c/a080bb69d30f11738d753a60d1eb733d627c2093 (opens in a new tab)
- https://git.kernel.org/stable/c/7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2 (opens in a new tab)
- https://git.kernel.org/stable/c/36e3f13bf0728f4ce11ee8904cec82a783222f62 (opens in a new tab)
- https://git.kernel.org/stable/c/32ac1b0b7f1cfa0d1a1faf9c72f4154046101070 (opens in a new tab)
- https://git.kernel.org/stable/c/ee5a386cfe60f3f8286de16a9db8e1a08f0bc124 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76622 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89710)Record last updated .