Answer in brief
CVE-2026-68450 records a Unknown severity vulnerability in btrfs: free mapping node on duplicate reloc root insert. The current sources do not mark it as known exploited. The current feed maps 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <92bedc0455552b42ada1a1f42b0e3a8593cdfccc || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <14a8be9428435ee17f17fae7991215c246b7fd43 || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <797dc567146c7e3c4f8d9680e4fbc76e0a6d9151 || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <ae0629ff9ccb836416ada129f4edc7efea6eaaad || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <6a8269b6459ed870a8156c106a0f597383907872 | 92bedc0455552b42ada1a1f42b0e3a8593cdfccc, 14a8be9428435ee17f17fae7991215c246b7fd43, 797dc567146c7e3c4f8d9680e4fbc76e0a6d9151, ae0629ff9ccb836416ada129f4edc7efea6eaaad, 6a8269b6459ed870a8156c106a0f597383907872 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: free mapping node on duplicate reloc root insert __add_reloc_root() allocates a mapping_node before inserting it into rc->reloc_root_tree. If rb_simple_insert() finds an existing entry, it returns the existing rb_node and leaves the newly allocated node unlinked. The error path then returns -EEXIST without freeing the new node. Since the node was never inserted into reloc_root_tree, the later cleanup in put_reloc_control() cannot find it either. Free the newly allocated node before returning -EEXIST. The callers currently assert that -EEXIST should not happen, so this is a defensive cleanup for an unexpected duplicate insert path. If the path is ever reached, the local allocation should still be released.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68450 records a Unknown severity vulnerability in btrfs: free mapping node on duplicate reloc root insert. The current sources do not mark it as known exploited. The current feed maps 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <92bedc0455552b42ada1a1f42b0e3a8593cdfccc || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <14a8be9428435ee17f17fae7991215c246b7fd43 || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <797dc567146c7e3c4f8d9680e4fbc76e0a6d9151 || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <ae0629ff9ccb836416ada129f4edc7efea6eaaad || >=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <6a8269b6459ed870a8156c106a0f597383907872 | 92bedc0455552b42ada1a1f42b0e3a8593cdfccc, 14a8be9428435ee17f17fae7991215c246b7fd43, 797dc567146c7e3c4f8d9680e4fbc76e0a6d9151, ae0629ff9ccb836416ada129f4edc7efea6eaaad, 6a8269b6459ed870a8156c106a0f597383907872 |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
In the Linux kernel, the following vulnerability has been resolved: btrfs: free mapping node on duplicate reloc root insert __add_reloc_root() allocates a mapping_node before inserting it into rc->reloc_root_tree. If rb_simple_insert() finds an existing entry, it returns the existing rb_node and leaves the newly allocated node unlinked. The error path then returns -EEXIST without freeing the new node. Since the node was never inserted into reloc_root_tree, the later cleanup in put_reloc_control() cannot find it either. Free the newly allocated node before returning -EEXIST. The callers currently assert that -EEXIST should not happen, so this is a defensive cleanup for an unexpected duplicate insert path. If the path is ever reached, the local allocation should still be released.
Quoted source text, attributed separately from HOL analysis.