btrfs: skip global block reserve accounting for rescue mounts
Summary
| CVE | CVE-2026-74571 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-15 13:18:02 UTC |
| Updated | 2026-08-17 06:19:55 UTC |
| 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. ] |
Risk And Classification
EPSS: 0.001450000 probability, percentile 0.043090000 (date 2026-08-17)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 8dbfc14fc736eb701089aff09645c3d4ad3decb1 076349e4c8d11f6b58c4549976a513b2b4dc6df2 git | Not specified |
| CNA | Linux | Linux | affected 8dbfc14fc736eb701089aff09645c3d4ad3decb1 51a0e8399858621442807a26057bcd1cd3ced046 git | Not specified |
| CNA | Linux | Linux | affected cbec34d3021d47007a0334c634f7053dbaf93d02 git | Not specified |
| CNA | Linux | Linux | affected 1e8087589b5cf6fa17adaf57b64cf1656d77dfec git | Not specified |
| CNA | Linux | Linux | affected 6.1.43 6.2 semver | Not specified |
| CNA | Linux | Linux | affected 6.4.8 6.5 semver | Not specified |
| CNA | Linux | Linux | affected 6.5 | Not specified |
| CNA | Linux | Linux | unaffected 6.5 semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.8 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/076349e4c8d11f6b58c4549976a513b2b4dc6df2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/51a0e8399858621442807a26057bcd1cd3ced046 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.