The Linux kernel's btrfs subsystem had a vulnerability where __add_reloc_root() allocated a mapping_node before inserting it into the reloc_root_tree. If rb_simple_insert() detected a duplicate entry, it returned the existing node and left the newly allocated node unlinked and not freed. This caused a memory leak since the cleanup function put_reloc_control() could not find the unlinked node to free it. The fix involves freeing the newly allocated node before returning the error code -EEXIST. This vulnerability is a defensive fix for an unexpected duplicate insert scenario.

The impact is limited to a potential memory leak in the btrfs filesystem code of the Linux kernel if a duplicate reloc root insert occurs. There is no indication of direct exploitation or broader security impact such as privilege escalation or denial of service. The callers currently assert that the duplicate insert should not happen, so this is a defensive fix to prevent resource leakage in an unexpected error path.

A fix has been applied to the Linux kernel to free the newly allocated mapping_node on detecting a duplicate insert in __add_reloc_root(). Users should update to a Linux kernel version that includes this fix once available. Patch status is not explicitly confirmed in the provided data; check the official Linux kernel advisories or vendor updates for the exact fixed versions and remediation guidance.