GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nfsd: dentry reference leak on every crafted NFSv3 filehandle against a V4ROOT export

UnscoredCVE-2026-89683Kernel, userspace & hypervisorcurated

Impact

nfsd_set_fh_dentry() drops the dentry reference returned by exportfs_decode_fh_raw() when an NFS3_FHSIZE or NFS_FHSIZE filehandle resolves to an NFSEXP_V4ROOT export: the error path calls exp_put() but never dput(), and fhp->fh_dentry was never set so fh_put() cannot clean up. A client that repeats such a request leaks a dentry reference per call, pinning dentries and their inodes indefinitely. Sustained, that is unbounded kernel memory growth and an unremovable mount on the NFS server, which in an HPC or GPU cluster is the shared dataset and checkpoint server every job depends on. The record carries no CVSS score and no CWE.

Who can reach it

Any client that can reach the NFS server's RPC port and send NFSv3 requests, using a filehandle crafted to carry the fsid of a V4ROOT export. No valid file access is needed - the leak happens on the lookup path before any permission decision. Servers that export nothing with the V4ROOT flag are not affected.

What to do

Patch the kernel on NFS servers with the stable commits linked in the record and reboot; nfsd is in-kernel, so there is no daemon-restart fix. Until then, the exposure can be narrowed by restricting which networks reach the server's NFS port and by reviewing whether any V4ROOT (NFSv4 pseudo-root) exports are actually needed. Rebooting a storage server means an outage window for every job holding its mounts.

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.