Answer in brief
CVE-2026-89645 records a Unknown severity vulnerability in btrfs: drop recovered reloc root refs on recovery failure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <2256d6dc5b88841a8a8b4fd9a9f04730705fb6fd || >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <8a64baeb5bbb706b83d2235c1e39f5b77183817f || >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <4d43107e807bcd92621106b07f5011411c6341a8 || >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <6d8ba4572922e336f0b59a80751b018e1e135164 | 2256d6dc5b88841a8a8b4fd9a9f04730705fb6fd, 8a64baeb5bbb706b83d2235c1e39f5b77183817f, 4d43107e807bcd92621106b07f5011411c6341a8, 6d8ba4572922e336f0b59a80751b018e1e135164 |
| Linux/Linuxgeneric | 5.7 | Not reported |
| Linux/Linuxgeneric | >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <7b8c6af17287899a5d00c70566831feac237d192 || >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <2256d6dc5b88841a8a8b4fd9a9f04730705fb6fd || >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <8a64baeb5bbb706b83d2235c1e39f5b77183817f || >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <4d43107e807bcd92621106b07f5011411c6341a8 || >=f44deb7442edf42abee6be25fca7e3e86061b4c9 <6d8ba4572922e336f0b59a80751b018e1e135164 | 7b8c6af17287899a5d00c70566831feac237d192, 2256d6dc5b88841a8a8b4fd9a9f04730705fb6fd, 8a64baeb5bbb706b83d2235c1e39f5b77183817f, 4d43107e807bcd92621106b07f5011411c6341a8, 6d8ba4572922e336f0b59a80751b018e1e135164 |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: drop recovered reloc root refs on recovery failure During relocation recovery, each fs root gets a reference to its relocation root. If loading or adding a later root fails, or if the first transaction commit fails, btrfs_recover_relocation() jumps to out_unset before merge_reloc_roots() and clean_dirty_subvols(). put_reloc_control() drops the list-owned relocation root references, but it does not clear fs_root->reloc_root or drop the references owned by those pointers. Mount cleanup only drops them when BTRFS_FS_ERROR is set, so an error such as -ENOMEM while processing a later root can leave references behind. Keep temporary references to the fs roots associated during recovery. On failure, clear their reloc_root pointers and drop the corresponding references. Once the first transaction commit succeeds, drop only the temporary fs root references and let the normal merge and cleanup paths handle the relocation roots. Fault injection on a pending-relocation image confirmed the cleanup gap. With an injected first-commit failure, 25 fs roots had reloc_root set with fs_error=0. With this fix, the same failure path drops that count to 0 before mount fails.
Quoted source text, attributed separately from HOL analysis.