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 3D3CE5AA69F for ; Thu, 17 Sep 2026 16:25:59 +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=1789662360; cv=none; b=GhYuCCV3yBBjrOg8TdNeZbUsSQe8CaFljPDY8KVRYBJydjEpzt6pBe34n+uaxoqbib6tITXo1qEklFhC8zaZ3KnneA4PeqcbX37k6fWroOojAx4mgtjIq622a/bidyJCfvSQy/xb+6RrAnL09ERP9/VYuGYhPQI2Vfp1cO070XA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789662360; c=relaxed/simple; bh=xF6J0YTOpJDjCD83Kae57XitE4NMQsRKDQRVetBCClk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=pe1SrnFqeu+ba16GWt7Qxk0/5Z43bIvDtQsjyzNp14kqFyX+HGq0MjNQ2Eg60CPLWOJUvdhxJM17o0VSJWMCsAiKz1pr2izITUBaDvSyBK+TjNoOrWLuxmd9nJel7V2h85FfbtoNQfPjPcOXXJ5NaOIRU8CwPUOcgLEcyblccBc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=W2pXAY9y; 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="W2pXAY9y" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8A6971F000FF; Thu, 17 Sep 2026 16:25:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789662359; bh=c98Glle2cza97DiFP4q6dGSUXWIT9vMptiqLEgg9FAQ=; h=From:To:Cc:Subject:Date:Reply-To; b=W2pXAY9yjaPiPi9ZzVKsy0WLqzwAgNO3hvfugqdlPr5l/9DMpwbk3rOEr1D0lt05c XHVCXDfd9QuNkin63YUtVu0mFtDUQ0nzLCdt0Z4NHXmNKh7ChTfI0c81CFNJ3TW54B zQNe2SguZP8A7TSm7KGof5aN7HS0LpafSxDJlIUs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-90280: phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend Date: Thu, 17 Sep 2026 17:11:50 +0100 Message-ID: <2026091750-CVE-2026-90280-eeeb@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=3035; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=3TI+7Vw9tLcGWTsrmNGDaga1iuslf6u5k4uXd1oZaFw=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlrBCY9iWCamuDc9Tfq5PYFL3XeJzUxCTz8OU2Zs+/T8 luu+1YxdMSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEXn5kmKf1tVmLS+nCi322 2e9i5nxYtKx8dzHD/NDHS7uDGafOufGhyPDUdFX7DeWfVgEA 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: phy: qcom: qmp-usb: Fix possible NULL-deref on early runtime suspend There is a small window where the runtime suspend callback may run after pm_runtime_enable() and before pm_runtime_forbid(). In this case, a crash occurs because runtime suspend/resume dereferences qmp->phy pointer, which is not yet initialized: `if (!qmp->phy->init_count) {` This can also happen if user re-enables runtime-pm via the sysfs attribute before qmp phy is initialized. Similarly to other qcom phy drivers, introduce a qmp->phy_initialized variable that can be used to avoid relying on the possibly uninitialized phy pointer. The Linux kernel CVE team has assigned CVE-2026-90280 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6 with commit e464a3180a43b6596bd267f9f274e1793bfb8150 and fixed in 6.6.157 with commit 9b28287c5dea7650e6dd317591b9e82b6e145365 Issue introduced in 6.6 with commit e464a3180a43b6596bd267f9f274e1793bfb8150 and fixed in 6.12.110 with commit f4e39ab1b2009a89c60e4cb9dbefb8140d405eff Issue introduced in 6.6 with commit e464a3180a43b6596bd267f9f274e1793bfb8150 and fixed in 6.18.52 with commit 5547fd950d6bf72de861b6934341e7bb0888640c Issue introduced in 6.6 with commit e464a3180a43b6596bd267f9f274e1793bfb8150 and fixed in 7.2.6 with commit 03455404fb6cbfd65842695df26739853fc1516b Issue introduced in 6.6 with commit e464a3180a43b6596bd267f9f274e1793bfb8150 and fixed in 7.3-rc1 with commit 142c5593379273264474f31d5956b1a0065cd576 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-90280 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-usb.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/9b28287c5dea7650e6dd317591b9e82b6e145365 https://git.kernel.org/stable/c/f4e39ab1b2009a89c60e4cb9dbefb8140d405eff https://git.kernel.org/stable/c/5547fd950d6bf72de861b6934341e7bb0888640c https://git.kernel.org/stable/c/03455404fb6cbfd65842695df26739853fc1516b https://git.kernel.org/stable/c/142c5593379273264474f31d5956b1a0065cd576