🛡️ CVE-2025-71299 — kernel

spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing

In the Linux kernel, the following vulnerability has been resolved:

spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing

The recent refactoring of where runtime PM is enabled done in commit

f1eb4e792bb1 ("spi: spi-cadence-quadspi: Enable pm runtime earlier to

avoid imbalance") made the fact that when we do a pm_runtime_disable()

in the error paths of probe() we can trigger a runtime disable which in

turn results in duplicate clock disables. This is particularly likely

to happen when there is missing or broken DT description for the flashes

attached to the controller.

Early on in the probe function we do a pm_runtime_get_noresume() since

the probe function leaves the device in a powered up state but in the

error path we can't assume that PM is enabled so we also manually

disable everything, including clocks. This means that when runtime PM is

active both it and the probe function release the same reference to the

main clock for the IP, triggering warnings from the clock subsystem:

[ 8.693719] clk:75:7 already disabled

[ 8.693791] WARNING: CPU: 1 PID: 185 at /usr/src/kernel/drivers/clk/clk.c:1188 clk_core_disable+0xa0/0xb

...

[ 8.694261] clk_core_disable+0xa0/0xb4 (P)

[ 8.694272] clk_disable+0x38/0x60

[ 8.694283] cqspi_probe+0x7c8/0xc5c [spi_cadence_quadspi]

[ 8.694309] platform_probe+0x5c/0xa4

Dealing with this issue properly is complicated by the fact that we

don't know if runtime PM is active so can't tell if it will disable the

clocks or not. We can, however, sidestep the issue for the flash

descriptions by moving their parsing to when we parse the controller

properties which also save us doing a bunch of setup which can never be

used so let's do that.