Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93798btrfs: fix reloc root cleanup in merge_reloc_roots()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 9 days 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

CVSS scores of CVE-2026-93798, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 1dae7e0e58b484eaa43d530f211098fdeeb0f404 – < 29531470b1bf1e8bd2df4941fe913106edbca615
    • affected 1dae7e0e58b484eaa43d530f211098fdeeb0f404 – < 415f8665a969d3c906e4fd7c90fcbb4b357886f6
    • affected 1dae7e0e58b484eaa43d530f211098fdeeb0f404 – < ee695a968aa73b1e67ccbf2133dc0e54381d32b2
    • affected 1dae7e0e58b484eaa43d530f211098fdeeb0f404 – < 0bc25f0a2d1b3e0a691431c4d7aef36afcd527c5
    • affected 1dae7e0e58b484eaa43d530f211098fdeeb0f404 – < ab48583aa9948205ff9a6470e23dbff74c565e24
    • affected 1dae7e0e58b484eaa43d530f211098fdeeb0f404 – < 63d6b1f04cd91c825329712aa526215ffa5d11ca
    • affected 1dae7e0e58b484eaa43d530f211098fdeeb0f404 – < b78fe9563e2d5ae47805f1e5dc722c91fd30e1f8
    • affected ee08663380ffd5a45a1c87580fbc305e8413c235
    • affected 33823378ff2b510fd7b566f25bb18438aeb9b23b
    • affected 5.4.54 – < 5.5
    • affected 5.7.11 – < 5.8
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93798 badge
[![CVE-2026-93798](https://cveledger.app/badge/CVE-2026-93798.svg)](https://cveledger.app/cve/CVE-2026-93798)

Record last updated .