clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cd52c2a4b5c43631e429d06dce12e08b0cab477f · < e1188332a9110cf3635fe286481ee38305b3c2b6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
clk: scpi: bound-check DVFS index in scpi_dvfs_recalc_rate
dvfs_get_idx() may return an out-of-range index if the SCP firmware is buggy or returns a stale value. Only negative indexes were rejected, so a large index walked past info->opps and could treat garbage as a clock rate (KASAN OOB / wrong frequency to consumers). The missing upper bound dates back to the original SCPI clock driver.
Treat indexes >= opp count as invalid and return 0, same as idx < 0.
From the CVE record · Linux
The SCPI clock driver did not reject DVFS indexes beyond the available operating points. If SCP firmware returns a buggy or stale index, the driver may read past the array and report an incorrect clock rate. The input does not specify an attack route, authentication requirements, or user interaction.
Engineers running Linux kernels with the SCPI clock driver should check their versions; affected versions are not specified.