CVE-2026-68450

btrfs: free mapping node on duplicate reloc root insert

N/A
Published: August 12, 2026 at 12:51 AM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.13 ≤ v < 5.15.2165.13 ≤ v < 6.1.1835.13 ≤ v < 6.12.1015.13 ≤ v < 6.18.425.13 ≤ v < 6.6.1485.13 ≤ v < 7.1.65.13 ≤ v < 7.25.1357a304cfd43b2b4a5b44b8f5dc026abb34183068
Vendor states this is fixed in 14a8be9428435ee17f17fae7991215c246b7fd43 (fixed)
Vendor states this is fixed in 29d9746812d8b7c37d594f484e994fd552c3ec33 (fixed)
Vendor states this is fixed in 6a8269b6459ed870a8156c106a0f597383907872 (fixed)
Vendor states this is fixed in 797dc567146c7e3c4f8d9680e4fbc76e0a6d9151 (fixed)
Vendor states this is fixed in 92bedc0455552b42ada1a1f42b0e3a8593cdfccc (fixed)
Vendor states this is fixed in ae0629ff9ccb836416ada129f4edc7efea6eaaad (fixed)
Vendor states this is fixed in b7c5b8e1d5f0779dfbabc3068b7ac0f12e53b3a8 (fixed)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card