CVE-2026-74571btrfs: skip global block reserve accounting for rescue mounts
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: skip global block reserve accounting for rescue mounts [BUG] Mounting with rescue=ibadroots after corrupting the block group tree root triggers a NULL pointer dereference: BUG: kernel NULL pointer dereference, address: 0000000000000100 RIP: 0010:btrfs_update_global_block_rsv+0x9d/0x1c0 [btrfs] Call Trace: fill_dummy_bgs+0xd4/0x120 [btrfs] open_ctree+0xc6e/0x1ca0 [btrfs] btrfs_get_tree+0x50d/0xa40 [btrfs] The same crash occurs with a corrupted raid stripe tree root, via btrfs_read_block_groups() instead of fill_dummy_bgs(). [CAUSE] With rescue=ibadroots, btrfs_read_roots() allows the mount to continue when either root cannot be read, leaving the corresponding root pointer NULL while its on-disk feature bit remains set. btrfs_update_global_block_rsv() then dereferences the missing root based on the feature bit alone. [FIX] Rescue mounts are fully read-only and cannot start transactions, so the global reserve is never consumed. Under btrfs_is_full_ro(), mark the reserve as full and return before performing the accounting. And since we need to check if the fs is mount fully RO, export fs_is_full_ro() as btrfs_is_full_ro(), and move it to fs.h. [ Squash the fs_is_full_ro() export commit into this one. ]
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected cbec34d3021d47007a0334c634f7053dbaf93d02 – < aa72cc4675240ab6b01ec72ac6a1fe832e715569
- affected 8dbfc14fc736eb701089aff09645c3d4ad3decb1 – < ca05d9abde2195cec3d07d0d4d65152d8171078f
- affected 8dbfc14fc736eb701089aff09645c3d4ad3decb1 – < 3a69fae2371a5ee190d4c4bbe5304a753558c1c6
- affected 8dbfc14fc736eb701089aff09645c3d4ad3decb1 – < 969a96479add6bd42d7f7241f99f27b31571a953
- affected 8dbfc14fc736eb701089aff09645c3d4ad3decb1 – < 076349e4c8d11f6b58c4549976a513b2b4dc6df2
- affected 8dbfc14fc736eb701089aff09645c3d4ad3decb1 – < 51a0e8399858621442807a26057bcd1cd3ced046
- affected 1e8087589b5cf6fa17adaf57b64cf1656d77dfec
- affected 6.1.43 – < 6.1.191
- affected 6.4.8 – < 6.5
- affected 6.5
- unaffected < 6.5
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.57 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/aa72cc4675240ab6b01ec72ac6a1fe832e715569 (opens in a new tab)
- https://git.kernel.org/stable/c/ca05d9abde2195cec3d07d0d4d65152d8171078f (opens in a new tab)
- https://git.kernel.org/stable/c/3a69fae2371a5ee190d4c4bbe5304a753558c1c6 (opens in a new tab)
- https://git.kernel.org/stable/c/969a96479add6bd42d7f7241f99f27b31571a953 (opens in a new tab)
- https://git.kernel.org/stable/c/076349e4c8d11f6b58c4549976a513b2b4dc6df2 (opens in a new tab)
- https://git.kernel.org/stable/c/51a0e8399858621442807a26057bcd1cd3ced046 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59636 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74571)Record last updated .