CVE-2026-80534: Linux kernel · xfs: fix ilock leak on error in xfs_dq_get_next_id
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-80534 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-80534 (opens in a new tab)
- git.kernel.org/stable/c/08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38 (opens in a new tab)
- git.kernel.org/stable/c/0865e4fca02e418fd2423fae9a887dee87b778a1 (opens in a new tab)
- git.kernel.org/stable/c/63320a0f70f66f311f4bccff3af0719c2119f46c (opens in a new tab)
- git.kernel.org/stable/c/e4c05ebd01e910bccd4f7e9517c7353982e27763 (opens in a new tab)
- git.kernel.org/stable/c/514a5d42d4188fc5f1499a8d654c717ebf981193 (opens in a new tab)
- git.kernel.org/stable/c/ed8bfb43de71213cfdbbe833b2c2817250e18b1a (opens in a new tab)
- git.kernel.org/stable/c/6401b99a285cd4cfb2949ba44675541b91ad7e4f (opens in a new tab)
- git.kernel.org/stable/c/e270d539b8a2e0cb8f617fee47a7b083c0088361 (opens in a new tab)