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-2023-53618btrfs: reject invalid reloc tree root keys with stack dump

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: reject invalid reloc tree root keys with stack dump [BUG] Syzbot reported a crash that an ASSERT() got triggered inside prepare_to_merge(). That ASSERT() makes sure the reloc tree is properly pointed back by its subvolume tree. [CAUSE] After more debugging output, it turns out we had an invalid reloc tree: BTRFS error (device loop1): reloc tree mismatch, root 8 has no reloc root, expect reloc root key (-8, 132, 8) gen 17 Note the above root key is (TREE_RELOC_OBJECTID, ROOT_ITEM, QUOTA_TREE_OBJECTID), meaning it's a reloc tree for quota tree. But reloc trees can only exist for subvolumes, as for non-subvolume trees, we just COW the involved tree block, no need to create a reloc tree since those tree blocks won't be shared with other trees. Only subvolumes tree can share tree blocks with other trees (thus they have BTRFS_ROOT_SHAREABLE flag). Thus this new debug output proves my previous assumption that corrupted on-disk data can trigger that ASSERT(). [FIX] Besides the dedicated fix and the graceful exit, also let tree-checker to check such root keys, to make sure reloc trees can only exist for subvolumes.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 months 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-2023-53618, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (15 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 259ee7754b6793af8bdd77f9ca818bc41cfe9541 – < 314135b7bae9618a317874ae195272682cf2d5d4
    • affected 259ee7754b6793af8bdd77f9ca818bc41cfe9541 – < 3ae93b316ca4b8b3c33798ef1d210355f2fb9318
    • affected 259ee7754b6793af8bdd77f9ca818bc41cfe9541 – < 84256e00eeca73c529fc6196e478cc89b8098157
    • affected 259ee7754b6793af8bdd77f9ca818bc41cfe9541 – < 6ebcd021c92b8e4b904552e4d87283032100796d
    • affected 3d95c52d789ca99e344061d7f6dadb2519adbcf5
    • affected fba904d68c8bbfcc89c2210cfcb2351be90bc3e5
    • affected 5.2.19 – < 5.3
    • affected 5.3.4 – < 5.4
  • Linux · Linux

    • affected 5.4
    • unaffected < 5.4
    • unaffected 5.15.127 – ≤ 5.15.*
    • unaffected 6.1.46 – ≤ 6.1.*
    • unaffected 6.4.11 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .