linux-cve-announce - CVE-2025-22009: regulator: dummy: force synchronous probing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025040842-CVE-2025-22009-2b2b@gregkh>
Date: Tue,  8 Apr 2025 10:16:43 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22009: regulator: dummy: force synchronous probing

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

regulator: dummy: force synchronous probing

Sometimes I get a NULL pointer dereference at boot time in kobject_get()
with the following call stack:

anatop_regulator_probe()
 devm_regulator_register()
  regulator_register()
   regulator_resolve_supply()
    kobject_get()

By placing some extra BUG_ON() statements I could verify that this is
raised because probing of the 'dummy' regulator driver is not completed
('dummy_regulator_rdev' is still NULL).

In the JTAG debugger I can see that dummy_regulator_probe() and
anatop_regulator_probe() can be run by different kernel threads
(kworker/u4:*).  I haven't further investigated whether this can be
changed or if there are other possibilities to force synchronization
between these two probe routines.  On the other hand I don't expect much
boot time penalty by probing the 'dummy' regulator synchronously.

The Linux kernel CVE team has assigned CVE-2025-22009 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.6.85 with commit e26f24ca4fb940b15e092796c5993142a2558bd9
	Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.12.21 with commit d3b83a1442a09b145006eb4294b1a963c5345c9c
	Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.13.9 with commit 5ade367b56c3947c990598df92395ce737bee872
	Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.14 with commit 8619909b38eeebd3e60910158d7d68441fc954e9

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-22009
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/dummy.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/e26f24ca4fb940b15e092796c5993142a2558bd9
	https://git.kernel.org/stable/c/d3b83a1442a09b145006eb4294b1a963c5345c9c
	https://git.kernel.org/stable/c/5ade367b56c3947c990598df92395ce737bee872
	https://git.kernel.org/stable/c/8619909b38eeebd3e60910158d7d68441fc954e9