NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f52188118d319b47d49ee91a897f6afda4879c59, Kernel 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070, Kernel 36e3f13bf0728f4ce11ee8904cec82a783222f62 and 10 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=fb700ef026766c95578aafc0db1b208946e7ad4f <f52188118d319b47d49ee91a897f6afda4879c59, >=fb700ef026766c95578aafc0db1b208946e7ad4f <32ac1b0b7f1cfa0d1a1faf9c72f4154046101070, >=fb700ef026766c95578aafc0db1b208946e7ad4f <36e3f13bf0728f4ce11ee8904cec82a783222f62, >=fb700ef026766c95578aafc0db1b208946e7ad4f <7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2, >=fb700ef026766c95578aafc0db1b208946e7ad4f <a080bb69d30f11738d753a60d1eb733d627c2093, >=fb700ef026766c95578aafc0db1b208946e7ad4f <ad3e41855325e55623276660ef20fbc3b8ba087f, >=fb700ef026766c95578aafc0db1b208946e7ad4f <ee5a386cfe60f3f8286de16a9db8e1a08f0bc124, =5.13 | f52188118d319b47d49ee91a897f6afda4879c59, 32ac1b0b7f1cfa0d1a1faf9c72f4154046101070, 36e3f13bf0728f4ce11ee8904cec82a783222f62, 7c5b0e813efd9124760d5fd1bfc6b229f03fb1a2, a080bb69d30f11738d753a60d1eb733d627c2093, ad3e41855325e55623276660ef20fbc3b8ba087f, ee5a386cfe60f3f8286de16a9db8e1a08f0bc124 |
| linux-kernel: Kernel | >=5.16.0 <6.1.188, >=6.13.0 <6.18.50, >=6.19.0 <7.2.4, >=6.2.0 <6.6.157, >=6.7.0 <6.12.109, >=5.13.0 <5.15.221 | 6.1.188, 6.18.50, 7.2.4, 6.6.157, 6.12.109, 5.15.221 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket