VDB

CVE-2026-89667

CVE-2026-89667 PUBLISHED CVSS 8.1 HIGH

nfsd: close shrinker/GC/fsnotify vs per-net shutdown race in filecache

Reported by linux · Published September 11, 2026

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.

EPSS 0.54% · 46.2th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.18-develAmazon Linux1:6.18.51-120.162.amzn2023
kernel-livepatch-6.18.51-120.162Amazon Linux1:1.0-0.amzn2023
kernel6.18-modules-extra-commonAmazon Linux1:6.18.51-120.162.amzn2023
kernel6.18-tools-develAmazon Linux1:6.18.51-120.162.amzn2023
kernel6.12Amazon Linux1:6.12.111-136.204.amzn2023

Risk scores

CVSS 3.1
8.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score
0.54%
46.2th percentile

Affected products

VendorProductVersions
LinuxLinuxffb402596147ac583f3464ff5c48feb9423e3838, ffb402596147ac583f3464ff5c48feb9423e3838, ffb402596147ac583f3464ff5c48feb9423e3838
LinuxLinux6.9, 0, 6.12.111
amazon:2023kernel6.18-devel0
amazon:2023kernel-livepatch-6.18.51-120.1620
amazon:2023kernel6.18-modules-extra-common0
amazon:2023kernel6.18-tools-devel0
amazon:2023kernel6.120
linuxlinux_kernel6.9, 6.9, 6.9
amazon:2023kernel6.12-headers0
amazon:2023kernel6.12-tools-devel0
LinuxLinux7.2.4, 6.18.51, *
amazon:2023microvm-kernel6.180
amazon:2023perf6.180
amazon:2023kernel6.18-modules-extra0
amazon:2023perf6.120
amazon:2023bpftool6.180
amazon:2023kernel6.12-modules-extra0
amazon:2023kernel6.180
amazon:2023kernel6.12-devel0
amazon:2023kernel-livepatch-6.12.111-136.2040

…and 7 more

Timeline

  • Sep 11, 2026 CVE Published
  • Sep 12, 2026 EPSS Score (29 in total, the first dated here)
  • Oct 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-89667
vulnetix vdb fixes CVE-2026-89667

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-89667/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›