| From bippy-7c5fe7eed585 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-22008: regulator: check that dummy regulator has been probed before using it |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| regulator: check that dummy regulator has been probed before using it |
| |
| Due to asynchronous driver probing there is a chance that the dummy |
| regulator hasn't already been probed when first accessing it. |
| |
| The Linux kernel CVE team has assigned CVE-2025-22008 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 5.10.236 with commit 3a9c46af5654783f99015727ac65bc2a23e2735a |
| Fixed in 5.15.180 with commit 8e500180904aae63afdce95cb378aeabe119ecda |
| Fixed in 6.1.132 with commit 270fe5c090f62dfce1cad0f5053e4827a6f50df4 |
| Fixed in 6.6.85 with commit 998b1aae22dca87da392ea35f089406cbef6032d |
| Fixed in 6.12.21 with commit a99f1254b11eaadd0794b74a8178bad92ab01cae |
| Fixed in 6.13.9 with commit 21e3fdf3146f9c63888d6bfabbd553434a5fb93f |
| Fixed in 6.14 with commit 2c7a50bec4958f1d1c84d19cde518d0e96a676fd |
| |
| 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-2025-22008 |
| 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/3a9c46af5654783f99015727ac65bc2a23e2735a |
| https://git.kernel.org/stable/c/8e500180904aae63afdce95cb378aeabe119ecda |
| https://git.kernel.org/stable/c/270fe5c090f62dfce1cad0f5053e4827a6f50df4 |
| https://git.kernel.org/stable/c/998b1aae22dca87da392ea35f089406cbef6032d |
| https://git.kernel.org/stable/c/a99f1254b11eaadd0794b74a8178bad92ab01cae |
| https://git.kernel.org/stable/c/21e3fdf3146f9c63888d6bfabbd553434a5fb93f |
| https://git.kernel.org/stable/c/2c7a50bec4958f1d1c84d19cde518d0e96a676fd |
