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 34D6C215774 for ; Wed, 26 Feb 2025 02:13:50 +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=1740536030; cv=none; b=De5ATWyy+FYW35DfJYouLtA3i+IzegPSO28k4FjRLD6nwJiEKlsx87HKS8tEoQ05B1Gk+xqqwNYzDtzIkRZ5yKmjZe/QElylEs4hyuaAsLMEnV4ZtFPB/UaHzTOq78qYgTHCgvg+pa2ns06yCcIW79NQ4fUC3BiV9q6KngZgk4E= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1740536030; c=relaxed/simple; bh=QYRNXMVS6J3KDoXuypBEEx7lRxSGaM/W+5TS5JJzdPM=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=L8EYul2P5d2+CpGU9Nhyn+NCRkUwSxRwTcV/4hwCGqiV2VkX2V9ye9N/ZQuP726v4bjycRU65nk6CnyDqlZB4zHprOWxcD2FzwQNYXOrIHZz4GqCjdV43Zfz9+LgGefYD4lSL5p9O3li6v5lMxeS28ExelGAU9P41eR6RTUw7/4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=C9IY5nS5; 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="C9IY5nS5" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0947AC4CEDD; Wed, 26 Feb 2025 02:13:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1740536030; bh=QYRNXMVS6J3KDoXuypBEEx7lRxSGaM/W+5TS5JJzdPM=; h=From:To:Cc:Subject:Date:Reply-to:From; b=C9IY5nS5ygHfGhGO9bwuGh5Dsg1+mO21AjJrUBmOZOfuXnU5wifkZzPTqdsTSGtiF hxtLNkMNThHVhBTuuAzoqxq4X1iBGPWp7eBAH6tlAfIw5QfpcEM3OmcEATAWg8k9nP 6cxN9xe3drnG5OrkqLuV+SeLfJuK0EFaSGvbNyXY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-49397: phy: qcom-qmp: fix struct clk leak on probe errors Date: Wed, 26 Feb 2025 03:11:11 +0100 Message-ID: <2025022650-CVE-2022-49397-fef3@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=3245; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=QYRNXMVS6J3KDoXuypBEEx7lRxSGaM/W+5TS5JJzdPM=; b=owGbwMvMwCRo6H6F97bub03G02pJDOn7yt8ZSb20aDxzyeRMhojJp0t99z3aD1Uf8f3tHd1fL vO0jGdeRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEykWJJhwcQ8jgM3755Wf+Ck 662Y1nnkudiURwzzC8VSPOe8M9ZxrZ36Wjvmnv1s5x/1AA== 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: phy: qcom-qmp: fix struct clk leak on probe errors Make sure to release the pipe clock reference in case of a late probe error (e.g. probe deferral). The Linux kernel CVE team has assigned CVE-2022-49397 to this issue. Affected and fixed versions =========================== Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 4.14.283 with commit b999d48b0869b8599de532ff6081575a7ab5358a Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 4.19.247 with commit 621a4bcfb7aa031e7760d7b156bad7a45df58387 Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 5.4.198 with commit 1668ad103679306ba2ef37f758d704e58a3ef1a0 Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 5.10.121 with commit 6f3673c8d8eff0c4ab5a5ee0d3ca9717d85419b4 Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 5.15.46 with commit b246695636a861a09f0e2cde92bb2dd8f114f024 Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 5.17.14 with commit f8d23895a41243c6a8dbf392e531fff9497bb023 Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 5.18.3 with commit ad9b0fad02f9b3a06ad5ac7df11f244e316a6254 Issue introduced in 4.12 with commit e78f3d15e115e8e764d4b1562b4fa538f2e22f6b and fixed in 5.19 with commit f0a4bc38a12f5a0cc5ad68670d9480e91e6a94df 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-49397 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: drivers/phy/qualcomm/phy-qcom-qmp.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/b999d48b0869b8599de532ff6081575a7ab5358a https://git.kernel.org/stable/c/621a4bcfb7aa031e7760d7b156bad7a45df58387 https://git.kernel.org/stable/c/1668ad103679306ba2ef37f758d704e58a3ef1a0 https://git.kernel.org/stable/c/6f3673c8d8eff0c4ab5a5ee0d3ca9717d85419b4 https://git.kernel.org/stable/c/b246695636a861a09f0e2cde92bb2dd8f114f024 https://git.kernel.org/stable/c/f8d23895a41243c6a8dbf392e531fff9497bb023 https://git.kernel.org/stable/c/ad9b0fad02f9b3a06ad5ac7df11f244e316a6254 https://git.kernel.org/stable/c/f0a4bc38a12f5a0cc5ad68670d9480e91e6a94df