Local kernel memory leak via duplicate relocation root
Published Aug 12, 2026 · Updated Aug 12, 2026
Memory leak in Linux kernel btrfs branches starting with 5.13 allows local users to consume kernel memory through duplicate relocation-root insertion. In __add_reloc_root(), rb_simple_insert() can reject a duplicate after allocation, while the -EEXIST path neither frees nor links the new mapping_node for later cleanup. The callers assert that this duplicate condition should not occur, so exploitation requires an unexpected relocation path; documented impact is limited to low availability loss.
Summary
What happened
Memory leak in Linux kernel btrfs branches starting with 5.13 allows local users to consume kernel memory through duplicate relocation-root insertion. In __add_reloc_root(), rb_simple_insert() can reject a duplicate after allocation, while the -EEXIST path neither frees nor links the new mapping_node for later cleanup. The callers assert that this duplicate condition should not occur, so exploitation requires an unexpected relocation path; documented impact is limited to low availability loss.
The record
- CVE
- CVE-2026-68450
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.13
- Affected versionversion=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <14a8be9428435ee17f17fae7991215c246b7fd43
- Affected versionversion=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <6a8269b6459ed870a8156c106a0f597383907872
- Affected versionversion=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <797dc567146c7e3c4f8d9680e4fbc76e0a6d9151
- Affected versionversion=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <92bedc0455552b42ada1a1f42b0e3a8593cdfccc
- Affected versionversion=57a304cfd43b2b4a5b44b8f5dc026abb34183068 <ae0629ff9ccb836416ada129f4edc7efea6eaaad
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo