GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux NFSD: filecache shutdown race leaks nfsd_file objects and their state

CVSS 8.1CVE-2026-89667Kernel, userspace & hypervisorcurated

Impact

The shrinker, GC worker, and fsnotify/lease callbacks can unhash an nfsd_file and then queue it to the per-net dispose list. If nfsd_file_cache_shutdown_net() runs concurrently, its rhashtable walk misses the unhashed file and its drain can run before the file is queued, so the file is left on a list nobody will drain. The result is a permanent leak of the file and its associated state on every affected net-namespace teardown - relevant to nodes that start and stop containerized NFS servers, where repeated teardowns accumulate unreclaimable kernel memory until reboot. Triggering it requires winning a race against shutdown; the record shows no path to memory corruption or privilege gain.

Who can reach it

Requires NFS server activity concurrent with a per-net nfsd shutdown, i.e. a local administrator or orchestration layer that stops nfsd in a network namespace while clients are still driving file cache churn. Not a path an unauthenticated remote client controls on its own.

What to do

Apply the stable fix, which widens nfsd_gc_lock over the dispose-list handoff in all three callers and adds a lock barrier in shutdown_net, then reboot the node. Until then, memory lost to the leak is only reclaimed by a reboot. The record names stable commits, not a released version.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.