CVE-2025-22009: regulator: dummy: force synchronous probing
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 kobjectget() with the following call stack:
anatopregulatorprobe() devmregulatorregister() regulatorregister() regulatorresolvesupply() kobjectget()
By placing some extra BUGON() statements I could verify that this is raised because probing of the 'dummy' regulator driver is not completed ('dummyregulatorrdev' is still NULL).
In the JTAG debugger I can see that dummyregulatorprobe() and anatopregulatorprobe() 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-22009?
CVE-2025-22009 is classified as a medium severity vulnerability that causes a NULL pointer dereference during the boot process.
How do I fix CVE-2025-22009?
To address CVE-2025-22009, update your Linux kernel to a version that includes the patch for this vulnerability.
What systems are affected by CVE-2025-22009?
CVE-2025-22009 affects various versions of the Linux kernel that utilize the dummy regulator.
What are the potential impacts of CVE-2025-22009?
The potential impact of CVE-2025-22009 includes system crashes or failure to boot due to a NULL pointer dereference.
When was CVE-2025-22009 resolved?
CVE-2025-22009 was resolved in the latest Linux kernel release following its identification.