Linux kernel out-of-bounds read in TPS65224 regulator ranges
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4
The TPS65224 BUCK2, BUCK3 and BUCK4 descriptors pass 4 as n_linear_ranges, but tps65224_bucks_2_3_4_ranges[] only has two entries, covering selectors 0x00-0x45.
The linear range helpers loop over n_linear_ranges entries, so any lookup of a selector above 0x45 reads past the end of the array and treats whatever follows it as two more ranges. This happens on the normal registration path when the core checks the voltage constraints against every selector. TPS652G1 uses the same descriptors and is affected too.
Use ARRAY_SIZE() so the count always matches the table.
From the CVE record · Linux
The Linux kernel's regulator driver gives an incorrect range count for TPS65224 BUCK2–4; TPS652G1 uses the same descriptors. During normal device registration, a voltage-selector lookup above 0x45 can read past the range table. The input does not describe an attacker path, authentication requirement, or user interaction.
Engineers running Linux kernels with the affected TPS65224 or TPS652G1 regulator descriptors should check their deployments; affected versions are not specified.