CVE-2026-93798 — btrfs: fix reloc root cleanup in merge_reloc_roots()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 1dae7e0e58b484eaa43d530f211098fdeeb0f404 and < 29531470b1bf1e8bd2df4941fe913106edbca615≥ 1dae7e0e58b484eaa43d530f211098fdeeb0f404 and < 415f8665a969d3c906e4fd7c90fcbb4b357886f6≥ 1dae7e0e58b484eaa43d530f211098fdeeb0f404 and < ee695a968aa73b1e67ccbf2133dc0e54381d32b2≥ 1dae7e0e58b484eaa43d530f211098fdeeb0f404 and < 0bc25f0a2d1b3e0a691431c4d7aef36afcd527c5≥ 1dae7e0e58b484eaa43d530f211098fdeeb0f404 and < ab48583aa9948205ff9a6470e23dbff74c565e24≥ 1dae7e0e58b484eaa43d530f211098fdeeb0f404 and < 63d6b1f04cd91c825329712aa526215ffa5d11ca≥ 1dae7e0e58b484eaa43d530f211098fdeeb0f404 and < b78fe9563e2d5ae47805f1e5dc722c91fd30e1f8version ee08663380ffd5a45a1c87580fbc305e8413c235 and 4 moreversion 33823378ff2b510fd7b566f25bb18438aeb9b23b≥ 5.4.54 and < 5.5≥ 5.7.11 and < 5.8version 5.8 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 7.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
7 on the record
- git.kernel.org/stable/c/0bc25f0a2d1b3e0a691431c4d7aef36afcd527c5
- git.kernel.org/stable/c/63d6b1f04cd91c825329712aa526215ffa5d11ca
- git.kernel.org/stable/c/415f8665a969d3c906e4fd7c90fcbb4b357886f6
- git.kernel.org/stable/c/b78fe9563e2d5ae47805f1e5dc722c91fd30e1f8
- git.kernel.org/stable/c/ee695a968aa73b1e67ccbf2133dc0e54381d32b2
- git.kernel.org/stable/c/29531470b1bf1e8bd2df4941fe913106edbca615
- git.kernel.org/stable/c/ab48583aa9948205ff9a6470e23dbff74c565e24
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 20h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 20h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-93798 is "btrfs: fix reloc root cleanup in merge_reloc_roots()", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.