Linux Kernel up to 7.1.9 XFS xfs_dq_get_next_id release of resource

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.61-

Summaryinfo

A vulnerability marked as critical has been reported in Linux Kernel up to 7.1.9. The affected element is the function xfs_dq_get_next_id of the component XFS. The manipulation leads to release of resource. This vulnerability is traded as CVE-2026-80534. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.9. It has been rated as critical. This issue affects the function xfs_dq_get_next_id of the component XFS. The manipulation with an unknown input leads to a release of resource vulnerability. Using CWE to declare the problem leads to CWE-772. The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. Impacted is availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-80534 since 08/26/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/26/2026). The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

Upgrading to version 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch 6401b99a285cd4cfb2949ba44675541b91ad7e4f/0865e4fca02e418fd2423fae9a887dee87b778a1/ed8bfb43de71213cfdbbe833b2c2817250e18b1a/e270d539b8a2e0cb8f617fee47a7b083c0088361/514a5d42d4188fc5f1499a8d654c717ebf981193/08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38/63320a0f70f66f311f4bccff3af0719c2119f46c is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Release of resource
CWE: CWE-772 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.217/6.1.184/6.6.153/6.12.105/6.18.46/7.1.10
Patch: 6401b99a285cd4cfb2949ba44675541b91ad7e4f/0865e4fca02e418fd2423fae9a887dee87b778a1/ed8bfb43de71213cfdbbe833b2c2817250e18b1a/e270d539b8a2e0cb8f617fee47a7b083c0088361/514a5d42d4188fc5f1499a8d654c717ebf981193/08bed2b67d2ee79d3e138c344d8dcfa4c9b26a38/63320a0f70f66f311f4bccff3af0719c2119f46c

Timelineinfo

08/26/2026 Advisory disclosed
08/26/2026 +0 days CVE reserved
08/26/2026 +0 days VulDB entry created
08/26/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80534 (🔒)
GCVE (CVE): GCVE-0-2026-80534
GCVE (VulDB): GCVE-100-395819

Entryinfo

Created: 08/26/2026 17:16
Changes: 08/26/2026 17:16 (59)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!