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 77135219A67 for ; Wed, 26 Feb 2025 02:15:41 +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=1740536141; cv=none; b=HKysGjGacyEKb/hLrQC27WDe/Dsa0vtrZ8G96pd9r30kZ2rvNcqEmGtdM4TtIRfDmQZyk6GaOjkhFhm1dy5VsTUX4aoiM0uaysijJ/wMCbp3GRHe554YGDtsXcR2abL+908U1k8NAQCnRwUtlXFI78uDO6tiDunYnDgmBbYfuws= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536141; c=relaxed/simple; bh=gYFm6F81ZRUDyzgYi0g09YfOZFog9k0jxVFfkpZrnBs=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=evio1AySgfQtOR8vWWG+bQpp9CP9VlJFa0bF8KqEZHo05Mor7XnxAepZFcPilXyfQiT3yxMoIo3GbHRk9T71q8LyzRL74S2X7hLzaZGqJPL5s0VRsEXzXudJnOyJokmu1DezSeqdmwzv93mbZANCWZEvc0Uk1jsJS344zJVbttk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=yNmOrEiT; 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="yNmOrEiT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 40A49C4CEE7; Wed, 26 Feb 2025 02:15:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536141; bh=gYFm6F81ZRUDyzgYi0g09YfOZFog9k0jxVFfkpZrnBs=; h=From:To:Cc:Subject:Date:Reply-to:From; b=yNmOrEiTUbCPqXDlZX54K3dVtHgELvOnUOXp5/RrJyiaif1t6j2R9k9TeOYcgyzvs mDQhtD/mp18NHrDTt5CT8ss0F7dBzBvz/q+NsVLE1WRSDyIvVAPsPIHBDPcZ6m8Kiv Y2v72pCnzbNDYUYHbzTX29IoXUs4ZacNU1opfkAg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49549: x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails Date: Wed, 26 Feb 2025 03:13:43 +0100 Message-ID: <2025022615-CVE-2022-49549-db30@gregkh> X-Mailer: git-send-email 2.48.1 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=3078; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=gYFm6F81ZRUDyzgYi0g09YfOZFog9k0jxVFfkpZrnBs=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7KtjfSTHJPVkcU80tv6VVUbM/Z8vxz+e/RTF/2yr8Y KZv/G79jlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIw0aGuRJHNaWW3dv4sml5 552yMqcTuz5JOjLMj9SI+h+qU/b/kYvdtdzSNQ4Cr9+yAAA= 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: x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails In mce_threshold_create_device(), if threshold_create_bank() fails, the previously allocated threshold banks array @bp will be leaked because the call to mce_threshold_remove_device() will not free it. This happens because mce_threshold_remove_device() fetches the pointer through the threshold_banks per-CPU variable but bp is written there only after the bank creation is successful, and not before, when threshold_create_bank() fails. Add a helper which unwinds all the bank creation work previously done and pass into it the previously allocated threshold banks array for freeing. [ bp: Massage. ] The Linux kernel CVE team has assigned CVE-2022-49549 to this issue. Affected and fixed versions =========================== Issue introduced in 5.8 with commit 6458de97fc15530b54477c4e2b70af653e8ac3d9 and fixed in 5.10.121 with commit b4acb8e7f1594607bc9017ef0aacb40b24a003d6 Issue introduced in 5.8 with commit 6458de97fc15530b54477c4e2b70af653e8ac3d9 and fixed in 5.15.46 with commit cc0dd4456f9573bf8af9b4d8754433918e809e1e Issue introduced in 5.8 with commit 6458de97fc15530b54477c4e2b70af653e8ac3d9 and fixed in 5.17.14 with commit 9708f1956eeb70c86943e0bc62fa3b0101b59616 Issue introduced in 5.8 with commit 6458de97fc15530b54477c4e2b70af653e8ac3d9 and fixed in 5.18.3 with commit 396b8e7ab2a99ddac57d3522b3da5e58cb608d37 Issue introduced in 5.8 with commit 6458de97fc15530b54477c4e2b70af653e8ac3d9 and fixed in 5.19 with commit e5f28623ceb103e13fc3d7bd45edf9818b227fd0 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-49549 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: arch/x86/kernel/cpu/mce/amd.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/b4acb8e7f1594607bc9017ef0aacb40b24a003d6 https://git.kernel.org/stable/c/cc0dd4456f9573bf8af9b4d8754433918e809e1e https://git.kernel.org/stable/c/9708f1956eeb70c86943e0bc62fa3b0101b59616 https://git.kernel.org/stable/c/396b8e7ab2a99ddac57d3522b3da5e58cb608d37 https://git.kernel.org/stable/c/e5f28623ceb103e13fc3d7bd45edf9818b227fd0