xfs: fix ilock leak on error in xfs_dq_get_next_id
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bda250dbaf39f67f8910e183853e4e6a9e5ce899 · < 514a5d42d4188fc5f1499a8d654c717ebf981193| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xfs: fix ilock leak on error in xfs_dq_get_next_id
xfs_dq_get_next_id() takes the quota inode ILOCK before calling xfs_iread_extents(). If xfs_iread_extents() 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.
From the CVE record · Linux
In the Linux kernel's XFS code, xfs_dq_get_next_id() can fail while reading extents and return without releasing the quota inode lock. Subsequent quota operations can hang; the input does not specify an attacker path, authentication requirement, or user interaction.
Anyone running Linux kernel versions with the affected XFS code should check their exposure; affected versions are not specified.