From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-22008: regulator: check that dummy regulator has been probed before using it
Date: Tue, 8 Apr 2025 10:16:42 +0200 [thread overview]
Message-ID: <2025040841-CVE-2025-22008-af1a@gregkh> (raw)
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 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/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
reply other threads:[~2025-04-08 8:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025040841-CVE-2025-22008-af1a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.