GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux NFSD: NFSv2 SETATTR reaches notify_change without a mount write reference

CVSS 9.1CVE-2026-89697Kernel, userspace & hypervisorcurated

Impact

In the BOTH_TIME_SET branch, fh_verify() is called early so setattr_prepare() can inspect the dentry, which makes nfsd_setattr() skip fh_want_write(). notify_change() then runs with no mount write reference, bypassing the freeze/remount-read-only protection that reference exists to provide. Practically this means an NFSv2 attribute change can modify a filesystem while it is being frozen or has been remounted read-only - an integrity and consistency problem for snapshot and backup workflows on shared storage nodes, not a path to code execution. The record gives no detail beyond the missing call, and NFSv2 is off or unused on most modern exports.

Who can reach it

An NFS client able to send a v2 SETATTR with both time fields set, against a server that still enables NFSv2. Export-level authentication applies; no local access needed.

What to do

Apply the stable fix adding the missing fh_want_write() after the early fh_verify(), and reboot the NFS server node. Disabling NFSv2 on the export removes exposure without a reboot. No fixed version is stated in the record.

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.