GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel NFSv4 client: dropped delegations leave the state manager looping on revoked state

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

Impact

Three error paths in nfs_inode_set_delegation() return without sending DELEGRETURN, so the server still believes the client holds a delegation the client has no record of. A later CB_RECALL is answered with NFS4ERR_BADHANDLE, the server revokes the delegation and parks it on cl_revoked, and because the client never sends FREE_STATEID the condition never drains: every SEQUENCE reply carries SEQ4_STATUS_RECALLABLE_STATE_REVOKED and the client's state manager loops issuing TEST_STATEID. The record notes the window is easy to reach now that servers hand out a write delegation on any write OPEN. For a fleet whose datasets and checkpoints live on NFS, the effect is a client stuck burning CPU in recovery with degraded or stalled I/O on that mount until the node is rebooted.

Who can reach it

Local - no attacker needed. It is a race between a delegation recall for one opener and a re-open that the server answers with a fresh write delegation, so any normal write workload on an NFSv4 mount can trigger it. Exposure is limited to nodes mounting NFSv4 with delegations in use.

What to do

Update to a stable kernel that returns the delegation on these error flows (five stable commits are linked; no single fixed version is given in the record). Kernel change on every NFS client node: drain and reboot. A node already in the looping state needs a reboot to clear it; remounting does not reset the server's revoked-state list.

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.