CVE-2023-53618btrfs: reject invalid reloc tree root keys with stack dump
- 5.5MediumCVSS base score
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
ID reserved
By Linux
Published
- 8 months later
· 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS: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)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- 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
- 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
- https://git.kernel.org/stable/c/314135b7bae9618a317874ae195272682cf2d5d4 (opens in a new tab)
- https://git.kernel.org/stable/c/3ae93b316ca4b8b3c33798ef1d210355f2fb9318 (opens in a new tab)
- https://git.kernel.org/stable/c/84256e00eeca73c529fc6196e478cc89b8098157 (opens in a new tab)
- https://git.kernel.org/stable/c/6ebcd021c92b8e4b904552e4d87283032100796d (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-32020 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53618)Record last updated .