AZL-59859
See a problem?- Import Source
- https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-59859.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/AZL-59859
- Upstream
- Published
- 2025-04-08T09:15:24Z
- Modified
- 2026-04-01T05:19:33.164223Z
- Severity
-
- 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- CVE-2025-22009 affecting package kernel for versions less than 6.6.85.1-2
- Details
-
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:
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 ('dummyregulator_rdev' 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.
- References