From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 5408B214208 for ; Thu, 27 Mar 2025 16:44:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743093875; cv=none; b=Y2xZgZZgwTIMmDfKyTO9dN9pD+nS/Hno3CS6RDvT5TDqRcGt4VJ9h0YPR/KMZvM6k7sm8LzsfVrkp4dl41zkkWiX/hsb5xabds3tyjsoFDjAVX4N4vQqIFBJ3L09IYuMd8f8DVOBzeLF8Uzl+oVRXkVcz0vlA3PtDxNpx8N1T+Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1743093875; c=relaxed/simple; bh=jhYUo+7kGisiMOWxFML/TidYneJjUuk4My/8X4+n9V0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=JMazWVKumFc2Kov0/XY0N1ZnTtF9dVHPIbkTv5jwYS1SYdbrSzJAIO5byNdyAIFRh7pYO73EcZ+xfuqluiXeSc0q/yrcnFcnPUhIYAnTpamT8JNjBMJDvRfKuWjegu9115op3lBphc6Rt2QzdbFemlpwTxlgKKXIdOHOFGnyx04= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Rar3p0w2; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="Rar3p0w2" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 42756C4CEDD; Thu, 27 Mar 2025 16:44:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1743093875; bh=jhYUo+7kGisiMOWxFML/TidYneJjUuk4My/8X4+n9V0=; h=From:To:Cc:Subject:Date:Reply-to:From; b=Rar3p0w2UzoiauxNRrXg1LX8XESNmon1f4Km7DylRUlKDpLI8b6ZuhFw60jNx779w +qmKP3ELPUL9HMDJqyEqKV3iYUdrn3ZgqYN9rF2EALQVQxjrXbqkG7loP7CHJPW8Ys WHUshw+lmoYajuGFg64xHA0SjjLowJfoxjEK/Ao0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49761: btrfs: always report error in run_one_delayed_ref() Date: Thu, 27 Mar 2025 17:43:19 +0100 Message-ID: <2025032703-CVE-2022-49761-9b1e@gregkh> X-Mailer: git-send-email 2.49.0 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=2966; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=jhYUo+7kGisiMOWxFML/TidYneJjUuk4My/8X4+n9V0=; b=owGbwMvMwCRo6H6F97bub03G02pJDOlPG8QnuNfL7lww/9BCOb1sqcuuuw6FLeyqL9mQGTmpP 6a4sai3I5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACaybyfD/GRTm8KFl059ibt7 vO3bwqjTaZJVaxnmCjb4zBXs/HrbRyU1QmjGm/i6mL4oAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: btrfs: always report error in run_one_delayed_ref() Currently we have a btrfs_debug() for run_one_delayed_ref() failure, but if end users hit such problem, there will be no chance that btrfs_debug() is enabled. This can lead to very little useful info for debugging. This patch will: - Add extra info for error reporting Including: * logical bytenr * num_bytes * type * action * ref_mod - Replace the btrfs_debug() with btrfs_err() - Move the error reporting into run_one_delayed_ref() This is to avoid use-after-free, the @node can be freed in the caller. This error should only be triggered at most once. As if run_one_delayed_ref() failed, we trigger the error message, then causing the call chain to error out: btrfs_run_delayed_refs() `- btrfs_run_delayed_refs() `- btrfs_run_delayed_refs_for_head() `- run_one_delayed_ref() And we will abort the current transaction in btrfs_run_delayed_refs(). If we have to run delayed refs for the abort transaction, run_one_delayed_ref() will just cleanup the refs and do nothing, thus no new error messages would be output. The Linux kernel CVE team has assigned CVE-2022-49761 to this issue. Affected and fixed versions =========================== Fixed in 5.10.165 with commit 18bd1c9c02e64a3567f90c83c2c8b855531c8098 Fixed in 5.15.90 with commit fdb4a70bb768d2a87890409597529ad81cb3de8a Fixed in 6.1.8 with commit 853ffa1511b058c79a4c9bb1407b3b20ce311792 Fixed in 6.2 with commit 39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92 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-2022-49761 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/extent-tree.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/18bd1c9c02e64a3567f90c83c2c8b855531c8098 https://git.kernel.org/stable/c/fdb4a70bb768d2a87890409597529ad81cb3de8a https://git.kernel.org/stable/c/853ffa1511b058c79a4c9bb1407b3b20ce311792 https://git.kernel.org/stable/c/39f501d68ec1ed5cd5c66ac6ec2a7131c517bb92