CVE-2026-89710

NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path

N/A
Published: September 11, 2026 at 07:46 PM UTC
Updated: October 19, 2026 at 09:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.13fb700ef026766c95578aafc0db1b208946e7ad4f
Vendor states this is fixed in 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070 (fixed)
Vendor states this is fixed in 36e3f13bf0728f4ce11ee8904cec82a783222f62 (fixed)
Vendor states this is fixed in 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2 (fixed)
Vendor states this is fixed in a080bb69d30f11738d753a60d1eb733d627c2093 (fixed)
Vendor states this is fixed in ad3e41855325e55623276660ef20fbc3b8ba087f (fixed)
Vendor states this is fixed in ee5a386cfe60f3f8286de16a9db8e1a08f0bc124 (fixed)
Vendor states this is fixed in f52188118d319b47d49ee91a897f6afda4879c59 (fixed)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card