btrfs: free mapping node on duplicate reloc root insert
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.13
References 7
git.kernel.org
- stable/c/29d9746812d8b7c37d594f484e994fd552c3ec33
- stable/c/b7c5b8e1d5f0779dfbabc3068b7ac0f12e53b3a8
- stable/c/92bedc0455552b42ada1a1f42b0e3a8593cdfccc
- stable/c/14a8be9428435ee17f17fae7991215c246b7fd43
- stable/c/797dc567146c7e3c4f8d9680e4fbc76e0a6d9151
- stable/c/ae0629ff9ccb836416ada129f4edc7efea6eaaad
- stable/c/6a8269b6459ed870a8156c106a0f597383907872