CVE-2025-22009

regulator: dummy: force synchronous probing

Medium · published April 8, 2025

CVSS v3.1
5.5
EPSS
0%
Percentile
9.0
In the wild
Unconfirmed
What it is

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 record
Technical detail
CVSS v3.1
5.5 · MEDIUM
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.00197 · 9.0th percentile
Published
2025-04-08T08:17Z
EPSS history
Timeline
  • 08 APR 08:17Z
    regulator: dummy: force synchronous probing
    cvelistv5