Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2025-22009

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.

Published

2025-04-08T09:15:24.460

Last Modified

2025-10-01T17:15:41.990

Status

Modified

Source

416baaa9-dc9f-4396-8d5f-8c081fb06d67

Severity

CVSSv3.1: 5.5 (MEDIUM)

Weaknesses
  • Type: Primary
    CWE-476
  • Type: Secondary
    CWE-476
Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Operating System linux linux_kernel < 6.6.85 Yes
Operating System linux linux_kernel < 6.12.21 Yes
Operating System linux linux_kernel < 6.13.9 Yes
Operating System linux linux_kernel 6.14 Yes
Operating System linux linux_kernel 6.14 Yes
Operating System linux linux_kernel 6.14 Yes
Operating System linux linux_kernel 6.14 Yes
Operating System linux linux_kernel 6.14 Yes
Operating System linux linux_kernel 6.14 Yes
Operating System linux linux_kernel 6.14 Yes
References