CVE-2026-93798

btrfs: fix reloc root cleanup in merge_reloc_roots()

HIGH
7.8
CVSS Score
Published: September 24, 2026 at 04:02 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix reloc root cleanup in merge_reloc_roots() If the root we got has zero root refs in its root item, we are resetting the root's ->reloc_root without using barriers like we do everywhere else. Sashiko complained about this while reviewing another patch, and it's correct (see the Link tag below). Also, we should not clear BTRFS_ROOT_DEAD_RELOC_TREE from the root unless the root points to the reloc root we have. Fix this by using clear_reloc_root(), which issues the memory barrier after setting the root's ->reloc_root to NULL and before clearing the bit BTRFS_ROOT_DEAD_RELOC_TREE from the root.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.4.54v ≥ 5.7.115.4.54 ≤ v < 5.55.7.11 ≤ v < 5.85.8 ≤ v < 5.10.2715.8 ≤ v < 5.15.2225.8 ≤ v < 6.1.1895.8 ≤ v < 6.12.1115.8 ≤ v < 6.18.535.8 ≤ v < 6.6.1585.8 ≤ v < 7.21dae7e0e58b484eaa43d530f211098fdeeb0f40433823378ff2b510fd7b566f25bb18438aeb9b23b5.4.545.7.115.8ee08663380ffd5a45a1c87580fbc305e8413c235
Vendor states this is fixed in 0bc25f0a2d1b3e0a691431c4d7aef36afcd527c5 (fixed)
Vendor states this is fixed in 29531470b1bf1e8bd2df4941fe913106edbca615 (fixed)
Vendor states this is fixed in 415f8665a969d3c906e4fd7c90fcbb4b357886f6 (fixed)
Vendor states this is fixed in 63d6b1f04cd91c825329712aa526215ffa5d11ca (fixed)
Vendor states this is fixed in ab48583aa9948205ff9a6470e23dbff74c565e24 (fixed)
Vendor states this is fixed in b78fe9563e2d5ae47805f1e5dc722c91fd30e1f8 (fixed)
Vendor states this is fixed in ee695a968aa73b1e67ccbf2133dc0e54381d32b2 (fixed)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Affected range stops below 5.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card