Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68450btrfs: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 13 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 57a304cfd43b2b4a5b44b8f5dc026abb34183068 – < 29d9746812d8b7c37d594f484e994fd552c3ec33
    • affected 57a304cfd43b2b4a5b44b8f5dc026abb34183068 – < b7c5b8e1d5f0779dfbabc3068b7ac0f12e53b3a8
    • affected 57a304cfd43b2b4a5b44b8f5dc026abb34183068 – < 92bedc0455552b42ada1a1f42b0e3a8593cdfccc
    • affected 57a304cfd43b2b4a5b44b8f5dc026abb34183068 – < 14a8be9428435ee17f17fae7991215c246b7fd43
    • affected 57a304cfd43b2b4a5b44b8f5dc026abb34183068 – < 797dc567146c7e3c4f8d9680e4fbc76e0a6d9151
    • affected 57a304cfd43b2b4a5b44b8f5dc026abb34183068 – < ae0629ff9ccb836416ada129f4edc7efea6eaaad
    • affected 57a304cfd43b2b4a5b44b8f5dc026abb34183068 – < 6a8269b6459ed870a8156c106a0f597383907872
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68450 badge
[![CVE-2026-68450](https://cveledger.app/badge/CVE-2026-68450.svg)](https://cveledger.app/cve/CVE-2026-68450)

Record last updated .