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 D2F6A3E123E for ; Wed, 3 Jun 2026 16:05:00 +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=1780502701; cv=none; b=Nvl94WpgyYTPLusGxhjsvBpjHLuwirXD30BBFiwWMQSAdRLyiT01WsfzD7+SfX8QOre6O3CiwbHG0pwOCeSJnw8OjCHyX/kiKeCyWc3YGI6Mt5EMMAPD0JXlnuHxjOd4jLNp91vXrR3dNp+PDSMpdw61cJdMxvc6nmglsZ7sD68= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780502701; c=relaxed/simple; bh=lwqjlfls2wlcYKFMXGD2ZZqMMZmIlh6MG6+soAj2ElI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=CJ6eiZfBX7jqecVeFkcO9HEDEuzVjz5mN2Cd5uR14cO35M4C9vs1dumTLfvjcVzg4KkmTIBWuBY6u+EXshrUb1Mbnshyz2h2QLsYIHURAIUa2mYm1+1E0RoRGh8gw9Iku8RR0PwYi+wF/xjSCAyOHxnClQpqRIrZiVHE7nLYflE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=p/2gaWPu; 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="p/2gaWPu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id D515E1F00893; Wed, 3 Jun 2026 16:04:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1780502700; bh=Ccw1x2IrdhdDKjI5n98cbwy/OaRmAyN+EGVgPbjSiXQ=; h=From:To:Cc:Subject:Date:Reply-To; b=p/2gaWPuePgcTd77PA7jEUyd9CfeldNwavvmKvANgkmvWNiFes/beX7a3TXmRVrbF 4cfNd0Mq7xkmo/s5uYZGj5iOcc13V/Hd/qS5TfzervNdMDOECMlVOiHslvRA7mkcFm bt83kmFQvGsd6C53AndF2WGcVL0NXOr4jxFL3zQ8= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-46252: regulator: core: fix locking in regulator_resolve_supply() error path Date: Wed, 3 Jun 2026 17:49:41 +0200 Message-ID: <2026060334-CVE-2026-46252-b147@gregkh> X-Mailer: git-send-email 2.54.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=2628; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=scPY1olrjaVMrj/i7MSR008WG0FzJe294tdcuTl67sI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkKvnw+75Y/SfcTm5tj/tUlNlxnrbxKnGn/j2Vy3M1aJ txJZfM7YlkYBJkYZMUUWb5s4zm6v+KQopeh7WmYOaxMIEMYuDgFYCJ/JBkWHNogH/L0+Jl3sas4 2/Ri9+zU/jQjgWHB7iQVu/Q952K3s6zcdO4XW96mrFefAA== 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: regulator: core: fix locking in regulator_resolve_supply() error path If late enabling of a supply regulator fails in regulator_resolve_supply(), the code currently triggers a lockdep warning: WARNING: drivers/regulator/core.c:2649 at _regulator_put+0x80/0xa0, CPU#6: kworker/u32:4/596 ... Call trace: _regulator_put+0x80/0xa0 (P) regulator_resolve_supply+0x7cc/0xbe0 regulator_register_resolve_supply+0x28/0xb8 as the regulator_list_mutex must be held when calling _regulator_put(). To solve this, simply switch to using regulator_put(). While at it, we should also make sure that no concurrent access happens to our rdev while we clear out the supply pointer. Add appropriate locking to ensure that. While the code in question will be removed altogether in a follow-up commit, I believe it is still beneficial to have this corrected before removal for future reference. The Linux kernel CVE team has assigned CVE-2026-46252 to this issue. Affected and fixed versions =========================== Issue introduced in 4.2 with commit 36a1f1b6ddc6d1442424e29548e790633ca39c7b and fixed in 6.19.4 with commit c66e0db0f37290b53c57994f998bb55590364fd0 Issue introduced in 4.2 with commit 36a1f1b6ddc6d1442424e29548e790633ca39c7b and fixed in 7.0 with commit 497330b203d2c59c5ff3fa4c34d14494d7203bc3 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-46252 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/regulator/core.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/c66e0db0f37290b53c57994f998bb55590364fd0 https://git.kernel.org/stable/c/497330b203d2c59c5ff3fa4c34d14494d7203bc3