From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 65795253B73 for ; Wed, 12 Aug 2026 00:52:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786495931; cv=none; b=CRsSPeeFvhjZfBGZfrFBoRX4eii/J0WjrBHdxEQRlTWsCpxQ1aNfP/McV4FpJX8G170/wLYGX/5GiCdvCrjRVxNlr40i2E0f6GKP90l6PMIwQn65Yr5EMZkC9IooSaAaWPcEIe068wa998WCCIFIcRB4L+I3uMl0smEyCHj2kwc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786495931; c=relaxed/simple; bh=/qk7d105ff9qqJ6vyi+XnxICpFcITaLBxOuKYkNzn9M=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=aFZ2wjW/a3AXy15fvJVGVWzSzJx6yPKPiUeyuye+RjswSpLi2OItH5YvQ3p6g5jWA5U4qlrA5E7Nj90epj8PtqbI2lTiiw7xgrVTbuJHvWlTw9+NbBfANRPI2HpQQGVhoU5jI+Z7+/clXPaTk1amlPEOfWDGc50i01G9LlbZD3o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=tRp+bt9+; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="tRp+bt9+" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 94E8A1F00A3A; Wed, 12 Aug 2026 00:52:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786495930; bh=Vj/iuH3HYD+oFTFmEYi/dBhXDSblw+vShizQoohFWXc=; h=From:To:Cc:Subject:Date:Reply-To; b=tRp+bt9+TNK0Tg31VPry/aNye68hdQZCQ4wC0DDrLp4a6xaM5TF2FBdNesVhO4mXA QCrF2JITNLomh/6rBiiAXRQ31/RUlrZRHZoDRvLRyrkpSJNzYe4RCaVOAPElJc1KrE xuhf+0EObGhJAbQLhB36NBrZecbEwkL28YxuiqyA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-68450: btrfs: free mapping node on duplicate reloc root insert Date: Wed, 12 Aug 2026 09:50:26 +0900 Message-ID: <2026081225-CVE-2026-68450-e589@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3133; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=ZIWQBmoralCGzwCQz6D0ZeYskBg/0bDgT4PPIZSbEoQ=; b=owGbwMvMwCRo6H6F97bub03G02pJDFnVhwN5PJIe52vt8zpwiWP3bN6Cx6Y8F7XfJiYpWK434 J9oaZLZEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABN5asKwoNsi5tlDR5VbIck3 19xN0XtpqL04jmGeSYV2nfwO42/bc28f/co987HKpfxIAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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. The Linux kernel CVE team has assigned CVE-2026-68450 to this issue. Affected and fixed versions =========================== Issue introduced in 5.13 with commit 57a304cfd43b2b4a5b44b8f5dc026abb34183068 and fixed in 6.6.148 with commit 92bedc0455552b42ada1a1f42b0e3a8593cdfccc Issue introduced in 5.13 with commit 57a304cfd43b2b4a5b44b8f5dc026abb34183068 and fixed in 6.12.101 with commit 14a8be9428435ee17f17fae7991215c246b7fd43 Issue introduced in 5.13 with commit 57a304cfd43b2b4a5b44b8f5dc026abb34183068 and fixed in 6.18.42 with commit 797dc567146c7e3c4f8d9680e4fbc76e0a6d9151 Issue introduced in 5.13 with commit 57a304cfd43b2b4a5b44b8f5dc026abb34183068 and fixed in 7.1.6 with commit ae0629ff9ccb836416ada129f4edc7efea6eaaad Issue introduced in 5.13 with commit 57a304cfd43b2b4a5b44b8f5dc026abb34183068 and fixed in 7.2-rc5 with commit 6a8269b6459ed870a8156c106a0f597383907872 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-68450 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: fs/btrfs/relocation.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/92bedc0455552b42ada1a1f42b0e3a8593cdfccc https://git.kernel.org/stable/c/14a8be9428435ee17f17fae7991215c246b7fd43 https://git.kernel.org/stable/c/797dc567146c7e3c4f8d9680e4fbc76e0a6d9151 https://git.kernel.org/stable/c/ae0629ff9ccb836416ada129f4edc7efea6eaaad https://git.kernel.org/stable/c/6a8269b6459ed870a8156c106a0f597383907872