xfs: fix ilock leak on error in xfs_dq_get_next_id
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.2%
exploitation probability
0.2%top 94% of all CVEs
observed exploitation
nono source reports it
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.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/0865e4fca02e418fd2423fae9a887dee87b778a1https://git.kernel.org/stable/c/08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38https://git.kernel.org/stable/c/514a5d42d4188fc5f1499a8d654c717ebf981193https://git.kernel.org/stable/c/63320a0f70f66f311f4bccff3af0719c2119f46chttps://git.kernel.org/stable/c/6401b99a285cd4cfb2949ba44675541b91ad7e4fhttps://git.kernel.org/stable/c/e270d539b8a2e0cb8f617fee47a7b083c0088361https://git.kernel.org/stable/c/e4c05ebd01e910bccd4f7e9517c7353982e27763https://git.kernel.org/stable/c/ed8bfb43de71213cfdbbe833b2c2817250e18b1a