296,172
Total vulnerabilities in the database
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.
Software | From | Fixed in |
---|---|---|
linux / linux_kernel | 6.14-rc1 | 6.14-rc1.x |
linux / linux_kernel | 6.14-rc2 | 6.14-rc2.x |
linux / linux_kernel | 6.14-rc3 | 6.14-rc3.x |
linux / linux_kernel | 6.14-rc4 | 6.14-rc4.x |
linux / linux_kernel | 6.13 | 6.13.9 |
linux / linux_kernel | 6.7 | 6.12.21 |
linux / linux_kernel | 6.4 | 6.6.85 |
linux / linux_kernel | 6.14-rc5 | 6.14-rc5.x |
linux / linux_kernel | 6.14-rc6 | 6.14-rc6.x |
linux / linux_kernel | 6.14-rc7 | 6.14-rc7.x |