CVE-2026-80534: xfs: fix ilock leak on error in xfs_dq_get_next_id
In the Linux kernel, the following vulnerability has been resolved:
xfs: fix ilock leak on error in xfsdqgetnextid
xfsdqgetnextid() takes the quota inode ILOCK before calling xfsireadextents(). If xfsireadextents() fails, the function returns immediately without releasing the lock, leaking the quota inode ILOCK. This can leave the quota inode locked and cause subsequent quota operations to hang.
Fix this by jumping to a common unlock path on error instead of returning directly.
Affected Software
Event History
Frequently Asked Questions
What systems are exposed to this issue?
Linux kernel systems using XFS quota operations are exposed when xfs_dq_get_next_id() encounters an xfs_iread_extents() error. The failure can leave the quota inode locked, causing later quota operations to hang.
What must occur for the hang to happen?
An error must occur in xfs_iread_extents() after xfs_dq_get_next_id() has acquired the quota inode ILOCK. The vulnerable error path returns without releasing that lock.
How can I tell whether a system is already affected?
A likely symptom is quota operations hanging because the quota inode remains locked after an extent-read error. The provided information does not identify a specific log message or other definitive detection indicator.
What should be done if patching cannot happen immediately?
The provided information only identifies the corrected behavior: the error path must release the quota inode ILOCK through a common unlock path. No temporary configuration workaround is provided.