CVE-2026-68450
btrfs: free mapping node on duplicate reloc root insert
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.
INFO
Published Date :
Aug. 12, 2026, 1:17 a.m.
Last Modified :
Aug. 12, 2026, 1:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-68450
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Free allocated mapping_node in the error path.
- Apply the kernel patch to fix the memory leak.
- Update the Linux kernel to the latest version.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-68450.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-68450 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-68450
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-68450 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-68450 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Aug. 12, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '57a304cfd43b2b4a5b44b8f5dc026abb34183068', 'lessThan': '92bedc0455552b42ada1a1f42b0e3a8593cdfccc', 'versionType': 'git'}, {'status': 'affected', 'version': '57a304cfd43b2b4a5b44b8f5dc026abb34183068', 'lessThan': '14a8be9428435ee17f17fae7991215c246b7fd43', 'versionType': 'git'}, {'status': 'affected', 'version': '57a304cfd43b2b4a5b44b8f5dc026abb34183068', 'lessThan': '797dc567146c7e3c4f8d9680e4fbc76e0a6d9151', 'versionType': 'git'}, {'status': 'affected', 'version': '57a304cfd43b2b4a5b44b8f5dc026abb34183068', 'lessThan': 'ae0629ff9ccb836416ada129f4edc7efea6eaaad', 'versionType': 'git'}, {'status': 'affected', 'version': '57a304cfd43b2b4a5b44b8f5dc026abb34183068', 'lessThan': '6a8269b6459ed870a8156c106a0f597383907872', 'versionType': 'git'}], 'programFiles': ['fs/btrfs/relocation.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.13'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.13', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.148', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.101', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.42', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.1.6', 'versionType': 'semver', 'lessThanOrEqual': '7.1.*'}, {'status': 'unaffected', 'version': '7.2-rc5', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['fs/btrfs/relocation.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/14a8be9428435ee17f17fae7991215c246b7fd43 Added Reference https://git.kernel.org/stable/c/6a8269b6459ed870a8156c106a0f597383907872 Added Reference https://git.kernel.org/stable/c/797dc567146c7e3c4f8d9680e4fbc76e0a6d9151 Added Reference https://git.kernel.org/stable/c/92bedc0455552b42ada1a1f42b0e3a8593cdfccc Added Reference https://git.kernel.org/stable/c/ae0629ff9ccb836416ada129f4edc7efea6eaaad