CVE-2026-80534: Linux kernel · xfs: fix ilock leak on error in xfs_dq_get_next_id
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ed8bfb43de71213cfdbbe833b2c2817250e18b1a : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:48 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in ed8bfb43de71213cfdbbe833b2c2817250e18b1a, e270d539b8a2e0cb8f617fee47a7b083c0088361, e4c05ebd01e910bccd4f7e9517c7353982e27763 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
This vulnerability has been fixed in several Linux kernel commits as listed in the established facts. Users and administrators should update to a Linux kernel version that includes these fixes. No additional mitigation is required once the system is updated.
Description
A vulnerability in the Linux kernel's XFS filesystem code causes a lock leak in the function xfs_dq_get_next_id when an error occurs in xfs_iread_extents. This leak can leave the quota inode locked, potentially causing subsequent quota operations to hang. The issue has been fixed by ensuring the lock is properly released on error paths.
References
- git.kernel.org/stable/c/e4c05ebd01e910bccd4f7e9517c7353982e27763 (opens in a new tab)
- git.kernel.org/stable/c/6401b99a285cd4cfb2949ba44675541b91ad7e4f (opens in a new tab)
- git.kernel.org/stable/c/0865e4fca02e418fd2423fae9a887dee87b778a1 (opens in a new tab)
- git.kernel.org/stable/c/ed8bfb43de71213cfdbbe833b2c2817250e18b1a (opens in a new tab)
- git.kernel.org/stable/c/e270d539b8a2e0cb8f617fee47a7b083c0088361 (opens in a new tab)
- git.kernel.org/stable/c/514a5d42d4188fc5f1499a8d654c717ebf981193 (opens in a new tab)
- git.kernel.org/stable/c/08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38 (opens in a new tab)
- git.kernel.org/stable/c/63320a0f70f66f311f4bccff3af0719c2119f46c (opens in a new tab)