Skip to main content
VulnerabilityPublished Updated

CVE-2026-80534: Linux kernel · xfs: fix ilock leak on error in xfs_dq_get_next_id

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ed8bfb43de71213cfdbbe833b2c2817250e18b1a : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:48 UTC

Severity
Medium

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

  1. Disclosed: evidence found.

    CVE published 26 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bda250dbaf39f67f8910e183853e4e6a9e5ce899, < ed8bfb43de71213cfdbbe833b2c2817250e18b1a
Fixed in
  • ed8bfb43de71213cfdbbe833b2c2817250e18b1a
LinuxLinuxAffected
  • ≥ bda250dbaf39f67f8910e183853e4e6a9e5ce899, < e270d539b8a2e0cb8f617fee47a7b083c0088361
Fixed in
  • e270d539b8a2e0cb8f617fee47a7b083c0088361
LinuxLinuxAffected
  • ≥ bda250dbaf39f67f8910e183853e4e6a9e5ce899, < e4c05ebd01e910bccd4f7e9517c7353982e27763
Fixed in
  • e4c05ebd01e910bccd4f7e9517c7353982e27763
LinuxLinuxAffected
  • ≥ bda250dbaf39f67f8910e183853e4e6a9e5ce899, < 63320a0f70f66f311f4bccff3af0719c2119f46c
Fixed in
  • 63320a0f70f66f311f4bccff3af0719c2119f46c
LinuxLinuxAffected
  • ≥ bda250dbaf39f67f8910e183853e4e6a9e5ce899, < 6401b99a285cd4cfb2949ba44675541b91ad7e4f
Fixed in
  • 6401b99a285cd4cfb2949ba44675541b91ad7e4f
LinuxLinuxAffected
  • ≥ bda250dbaf39f67f8910e183853e4e6a9e5ce899, < 0865e4fca02e418fd2423fae9a887dee87b778a1
Fixed in
  • 0865e4fca02e418fd2423fae9a887dee87b778a1

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

Community reviews

Loading reviews…