GPU VulnDB

Database/Control plane, storage & DevOps

Linux nfsd: filehandle composed from a stale dentry when dentry_create returns a different dentry

CVSS 9.8CVE-2026-89677Control plane, storage & DevOpscurated

Impact

nfsd4_create_file() called fh_compose() before it knew which dentry dentry_create() would hand back. If the exported filesystem returns a different dentry than the one passed in - the description gives re-exported NFS returning a filehandle matching a cached directory as the example - the dentry stored in resfhp can be freed and later dereferenced. The exposure is confined to servers re-exporting NFS or a similar filesystem that can substitute a dentry on OPEN; on a plain local export the described condition is hypothetical, and the commit message says so. Where it does apply, the NFS server backing a cluster's shared storage can be crashed by a client OPEN that creates a file.

Who can reach it

An NFSv4 client that can create files on an export, on a server where the underlying filesystem may return a substituted dentry (notably an NFS re-export). Normal client authentication only.

What to do

Update the NFS server kernel to a build containing one of the linked stable commits and reboot the server. Sites that do not re-export NFS or a filesystem with this behaviour can treat it as low priority and pick it up on the next scheduled kernel roll.

References

Related entries

All Control plane, storage & DevOps 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.