Linux Kernel up to 6.19.3 btrfs btrfs_quota_enable infinite loop

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.
5.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.3. It has been rated as critical. Affected is the function btrfs_quota_enable of the component btrfs. The manipulation leads to infinite loop. This vulnerability is listed as CVE-2026-45974. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.3 and classified as critical. This issue affects the function btrfs_quota_enable of the component btrfs. The manipulation with an unknown input leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid leaf access in btrfs_quota_enable() if ref key not found If btrfs_search_slot_for_read() returns 1, it means we did not find any key greater than or equals to the key we asked for, meaning we have reached the end of the tree and therefore the path is not valid. If this happens we need to break out of the loop and stop, instead of continuing and accessing an invalid path.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-45974 since 05/13/2026. Technical details are known, but no exploit is available.

Upgrading to version 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.14 or 6.19.4 eliminates this vulnerability. Applying the patch fd4913a53e3b54ad7e161847291439fe445d6356/b5b8ade9da452086e78f5d519b90d3769e354853/1ee1d006c9fe4d6be5527ab1c84216b80cccbe40/0761447f6f51e1c7997960d8e6559337deed6729/d7cf2314dd5e8661c05d076cd627eea9a7f76616/b2bd557b75b760e4b9d209112bda19314bd64558/ecb7c2484cfc83a93658907580035a8adf1e0a92 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best 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: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

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

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

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

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.10.252/5.15.202/6.1.165/6.6.128/6.12.75/6.18.14/6.19.4
Patch: fd4913a53e3b54ad7e161847291439fe445d6356/b5b8ade9da452086e78f5d519b90d3769e354853/1ee1d006c9fe4d6be5527ab1c84216b80cccbe40/0761447f6f51e1c7997960d8e6559337deed6729/d7cf2314dd5e8661c05d076cd627eea9a7f76616/b2bd557b75b760e4b9d209112bda19314bd64558/ecb7c2484cfc83a93658907580035a8adf1e0a92

Timelineinfo

05/13/2026 CVE reserved
05/27/2026 +14 days Advisory disclosed
05/27/2026 +0 days VulDB entry created
06/16/2026 +20 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-45974 (🔒)
GCVE (CVE): GCVE-0-2026-45974
GCVE (VulDB): GCVE-100-366233

Entryinfo

Created: 05/27/2026 17:19
Updated: 06/16/2026 10:28
Changes: 05/27/2026 17:19 (59), 06/16/2026 10:28 (10)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!