vulnerability
Ubuntu: (CVE-2023-53618): linux vulnerability
| Severity | CVSS | Published | Added | Modified |
|---|---|---|---|---|
| 5 | (AV:L/AC:L/Au:S/C:N/I:N/A:C) | Oct 7, 2025 | Oct 10, 2025 | Dec 2, 2025 |
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.
Solutions
References
- CVE-2023-53618
- https://attackerkb.com/topics/CVE-2023-53618
- URL-https://git.kernel.org/linus/6ebcd021c92b8e4b904552e4d87283032100796d
- URL-https://git.kernel.org/stable/c/314135b7bae9618a317874ae195272682cf2d5d4
- URL-https://git.kernel.org/stable/c/3ae93b316ca4b8b3c33798ef1d210355f2fb9318
- URL-https://git.kernel.org/stable/c/6ebcd021c92b8e4b904552e4d87283032100796d
- URL-https://git.kernel.org/stable/c/84256e00eeca73c529fc6196e478cc89b8098157
- URL-https://www.cve.org/CVERecord?id=CVE-2023-53618
Explore Exposure Command
Confidently identify and prioritize exposures from endpoint to cloud with full attack surface visibility and threat-aware risk context.