Inconsistent relocation state via unordered cleanup
Published Sep 24, 2026 · Updated Sep 24, 2026
Synchronization flaw in btrfs relocation cleanup in Linux before 6.12.111 and before 6.18.53 allows local users to corrupt relocation state. The merge_reloc_roots() function clears root->reloc_root without the required memory barrier and clears BTRFS_ROOT_DEAD_RELOC_TREE even when the root references a different relocation root. Triggering the faulty path requires a privileged btrfs balance or relocation operation with a relocation root that has zero references; no crash or data-loss outcome is documented.
Summary
What happened
Synchronization flaw in btrfs relocation cleanup in Linux before 6.12.111 and before 6.18.53 allows local users to corrupt relocation state. The merge_reloc_roots() function clears root->reloc_root without the required memory barrier and clears BTRFS_ROOT_DEAD_RELOC_TREE even when the root references a different relocation root. Triggering the faulty path requires a privileged btrfs balance or relocation operation with a relocation root that has zero references; no crash or data-loss outcome is documented.
The record
- CVE
- CVE-2026-93798
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.12.111
- Affected versionversion=0 <6.18.53
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <63d6b1f04cd91c825329712aa526215ffa5d11ca
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ab48583aa9948205ff9a6470e23dbff74c565e24
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b78fe9563e2d5ae47805f1e5dc722c91fd30e1f8
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started