CVE-2026-80534

xfs: fix ilock leak on error in xfs_dq_get_next_id

N/A

Published: August 26, 2026 at 02:37 PM UTC

Updated: August 27, 2026 at 01:31 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

4.13 ≤ v < 5.10.2674.13 ≤ v < 5.15.2174.13 ≤ v < 6.1.1844.13 ≤ v < 6.12.1054.13 ≤ v < 6.18.464.13 ≤ v < 6.6.1534.13 ≤ v < 7.1.104.13 ≤ v < 7.24.13bda250dbaf39f67f8910e183853e4e6a9e5ce899

Vendor states this is fixed in 0865e4fca02e418fd2423fae9a887dee87b778a1 (fixed)

Vendor states this is fixed in 08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38 (fixed)

Vendor states this is fixed in 514a5d42d4188fc5f1499a8d654c717ebf981193 (fixed)

Vendor states this is fixed in 63320a0f70f66f311f4bccff3af0719c2119f46c (fixed)

Vendor states this is fixed in 6401b99a285cd4cfb2949ba44675541b91ad7e4f (fixed)

Vendor states this is fixed in e270d539b8a2e0cb8f617fee47a7b083c0088361 (fixed)

Vendor states this is fixed in e4c05ebd01e910bccd4f7e9517c7353982e27763 (fixed)

Vendor states this is fixed in ed8bfb43de71213cfdbbe833b2c2817250e18b1a (fixed)

Vendor states this is fixed in 4.13 (unaffected)

Vendor states this is fixed in 5.10.267 (unaffected)

Vendor states this is fixed in 5.15.217 (unaffected)

Vendor states this is fixed in 6.1.184 (unaffected)