xfs: fix ilock leak on error in xfs_dq_get_next_id
Summary
| CVE | CVE-2026-80534 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-26 15:17:07 UTC |
| Updated | 2026-08-27 13:18:38 UTC |
| Description | 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. |
Risk And Classification
EPSS: 0.001720000 probability, percentile 0.067560000 (date 2026-08-27)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 e4c05ebd01e910bccd4f7e9517c7353982e27763 git | Not specified |
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 6401b99a285cd4cfb2949ba44675541b91ad7e4f git | Not specified |
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 0865e4fca02e418fd2423fae9a887dee87b778a1 git | Not specified |
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 ed8bfb43de71213cfdbbe833b2c2817250e18b1a git | Not specified |
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 e270d539b8a2e0cb8f617fee47a7b083c0088361 git | Not specified |
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 514a5d42d4188fc5f1499a8d654c717ebf981193 git | Not specified |
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38 git | Not specified |
| CNA | Linux | Linux | affected bda250dbaf39f67f8910e183853e4e6a9e5ce899 63320a0f70f66f311f4bccff3af0719c2119f46c git | Not specified |
| CNA | Linux | Linux | affected 4.13 | Not specified |
| CNA | Linux | Linux | unaffected 4.13 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.267 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.217 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.184 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.153 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.105 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.46 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.10 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/63320a0f70f66f311f4bccff3af0719c2119f46c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e4c05ebd01e910bccd4f7e9517c7353982e27763 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e270d539b8a2e0cb8f617fee47a7b083c0088361 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0865e4fca02e418fd2423fae9a887dee87b778a1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ed8bfb43de71213cfdbbe833b2c2817250e18b1a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/514a5d42d4188fc5f1499a8d654c717ebf981193 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6401b99a285cd4cfb2949ba44675541b91ad7e4f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.