GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel nfsd: NFSv4 SETATTR with the special ONE stateid NULL-derefs and oopses the server

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

Impact

A SETATTR carrying FATTR4_WORD2_TIME_DELEG_ACCESS or TIME_DELEG_MODIFY sets deleg_attrs and then dereferences the stateid pointer unconditionally. The NFSv4 all-0xFF "one stateid" validates successfully without populating that pointer, so the server oopses at a NULL offset. The commit message states this is remotely triggerable by any NFSv4 client with a single COMPOUND, with no authentication, delegation or prior state. That makes it the sharpest item in this batch for anyone whose GPU fleet mounts a Linux NFS server: one packet from any host that can open port 2049 halts the file server, and every node holding a mount stalls with it.

Who can reach it

Anyone who can reach the nfsd TCP port and speak NFSv4 - no authentication, no existing state, no delegation required. Exposure is whatever your export and firewall policy allows, which on a storage VLAN is usually every tenant node.

What to do

Update the host kernel to a stable release containing the NULL guard and reboot the NFS server; the fix is in kernel code with no runtime toggle. Until the window opens, restrict reachability of port 2049 to known client subnets - that limits who can send the COMPOUND, it does not remove the bug.

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.