CVE-2026-89682

published 11 Sep 2026 · updated 17 Nov 2026

nfsd: fix fcache_disposal UAF by inlining dispose state into nfsd_net

8.1HighCVSS 8.1EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 5.16, Kernel 41fe0e804bbf1110c0aba2ebdfc729efb240d8a6, Kernel 9c8ac7c2b9b150e13b7ad0d0fae54f17747dce67 and 10 more.

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix fcache_disposal UAF by inlining dispose state into nfsd_net nfsd_file_dispose_list_delayed() defers fput() to nfsd service threads via a per-net freeme queue, preventing the shrinker and GC worker from bearing the cost of closing files (see ffb402596147). However, the queue lives in a separately-allocated struct nfsd_fcache_disposal that is freed by nfsd_free_fcache_disposal_net() during per-net teardown. The global shrinker, laundrette, and fsnotify callbacks can still be inside nfsd_file_dispose_list_delayed() dereferencing that pointer, causing a use-after-free. Inline the spinlock and freeme list directly into struct nfsd_net (as fcache_dispose_lock and fcache_dispose_list), eliminating the separately allocated struct nfsd_fcache_disposal entirely. These fields now have the same lifetime as the net namespace itself, so there is no dangling pointer to chase. nfsd_file_cache_start_net() now just initializes the inline fields and cannot fail due to allocation. nfsd_file_cache_shutdown_net() drains the inline list directly instead of freeing a separate struct. The alloc/free helpers are removed.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.15.154 <5.16, >=1463b38e7cf34d4cc60f41daff459ad807b2e408 <41fe0e804bbf1110c0aba2ebdfc729efb240d8a6, >=1463b38e7cf34d4cc60f41daff459ad807b2e408 <9c8ac7c2b9b150e13b7ad0d0fae54f17747dce67, >=1463b38e7cf34d4cc60f41daff459ad807b2e408 <ba0ee9e04b7a0356c28d5a2fe445db675d24e572, >=1463b38e7cf34d4cc60f41daff459ad807b2e408 <bbf13732f74351d21c5e0e8dd9bd8e1c48dc35d4, >=1463b38e7cf34d4cc60f41daff459ad807b2e408 <cadc9036d5a8209f89e7026ddba7cfb1c716b03c, >=1463b38e7cf34d4cc60f41daff459ad807b2e408 <e6c3a43d0a41f03abae3764fc82a59369360c7e0, >=5.10.220 <5.11, =3bc94fb44f10ef852723e1aeaac6794c5ab16aec, =5.17, =e8f923e1e9fcc0832a12c8a2461792e5a9544c035.16, 41fe0e804bbf1110c0aba2ebdfc729efb240d8a6, 9c8ac7c2b9b150e13b7ad0d0fae54f17747dce67, ba0ee9e04b7a0356c28d5a2fe445db675d24e572, bbf13732f74351d21c5e0e8dd9bd8e1c48dc35d4, cadc9036d5a8209f89e7026ddba7cfb1c716b03c, e6c3a43d0a41f03abae3764fc82a59369360c7e0, 5.11
linux-kernel: Kernel>=5.15.154 <5.16, >=5.17.0 <6.1.191, >=6.13.0 <6.18.51, >=6.19.0 <7.2.4, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114, >=5.10.220 <5.115.16, 6.1.191, 6.18.51, 7.2.4, 6.6.160, 6.12.114, 5.11

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-89682 severity on Zeptric[![CVE-2026-89682](https://zeptric.io/badge/cve/CVE-2026-89682.svg)](https://zeptric.io/cve/CVE-2026-89682)