CVE-2026-68450

Unknown

Last modified

CVE-2026-68450 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 57a304cfd43b2b4a5b44b8f5dc026abb34183068, < 92bedc0455552b42ada1a1f42b0e3a8593cdfccc; >= 57a304cfd43b2b4a5b44b8f5dc026abb34183068, < 14a8be9428435ee17f17fae7991215c246b7fd43; >= 57a304cfd43b2b4a5b44b8f5dc026abb34183068, < 797dc567146c7e3c4f8d9680e4fbc76e0a6d9151; >= 57a304cfd43b2b4a5b44b8f5dc026abb34183068, < ae0629ff9ccb836416ada129f4edc7efea6eaaad; >= 57a304cfd43b2b4a5b44b8f5dc026abb34183068, < 6a8269b6459ed870a8156c106a0f597383907872
LinuxLinux5.13

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68450?
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.
How severe is CVE-2026-68450?
Severity scoring for CVE-2026-68450 is pending analysis.
How do I fix CVE-2026-68450?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-68450?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST