GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nfsd: file returned by dentry_create() may not actually be open before use

CVSS 7.5CVE-2026-89687Kernel, userspace & hypervisorcurated

Impact

->atomic_open may return success via finish_no_open() without opening the file, so dentry_create() can hand nfsd a file with FMODE_OPENED clear that nfsd then uses anyway. The commit itself calls this extremely unlikely - atomic_open handlers use finish_no_open() for already-existing files, where dentry_create() is not called, and the locked parent should prevent the race - and describes the change as caution rather than a demonstrated exploit. Listed here because NVD scores it 7.5 and it lands on the same NFS server path as the rest of this batch; treat it as low priority next to the remotely triggerable oopses.

Who can reach it

Server-side NFS file-creation path; no demonstrated attacker-controlled trigger is described in the record. Any exposure would be through a filesystem whose atomic_open returns success without opening.

What to do

Picked up with the same stable-kernel update as the other nfsd fixes in this batch - update the host kernel and reboot the NFS server. Not worth its own maintenance window; roll it in with the CVE-2026-89679 patch.

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.