CVE-2026-45974 | btrfs: fix invalid leaf access in btrfs_quota_enable() if ref key not found

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.

Published: 2026-05-27 Last update: 2026-06-17 Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-45974 is rated Low Risk (22.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.13%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-45974

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-16 0.18% 0.13% -0.06%
2 2026-06-15 0.02% 0.18% +0.16%
3 2026-05-28 — 0.02% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-45974

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2026-45974

GitHub Security Advisory for CVE-2026-45974

GHSA-9f93-r4x7-fg5m · Severity: medium — In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid leaf...

OS Trackers for CVE-2026-45974

vendor priority summary link
debian not yet assigned CVE-2026-45974 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-45974
redhat medium — https://access.redhat.com/security/cve/CVE-2026-45974
suse medium — https://www.suse.com/security/cve/CVE-2026-45974/
ubuntu medium CVE-2026-45974 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1422 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 1024, ignored 169, released 84, needed 71, not-affected 55, pending 18, needs-triage 1. https://ubuntu.com/security/CVE-2026-45974

Affected software / configurations for CVE-2026-45974

Vendor Product Version Raw CPE
linux linux_kernel >= 5.9.7, < 5.10 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.10.1, < 5.10.252 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.11, < 5.15.202 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 5.16, < 6.1.165 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.2, < 6.6.128 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.7, < 6.12.75 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.13, < 6.18.14 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel >= 6.19, < 6.19.4 cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux linux_kernel 5.10 cpe:2.3:o:linux:linux_kernel:5.10:-:*:*:*:*:*:*
linux linux_kernel 5.10 cpe:2.3:o:linux:linux_kernel:5.10:rc2:*:*:*:*:*:*
linux linux_kernel 5.10 cpe:2.3:o:linux:linux_kernel:5.10:rc3:*:*:*:*:*:*
linux linux_kernel 5.10 cpe:2.3:o:linux:linux_kernel:5.10:rc4:*:*:*:*:*:*
linux linux_kernel 5.10 cpe:2.3:o:linux:linux_kernel:5.10:rc5:*:*:*:*:*:*
linux linux_kernel 5.10 cpe:2.3:o:linux:linux_kernel:5.10:rc6:*:*:*:*:*:*
linux linux_kernel 5.10 cpe:2.3:o:linux:linux_kernel:5.10:rc7:*:*:*:*:*:*

References for CVE-2026-45974

cvelogic Threat Intelligence