Live › vulnerability › CVE-2026-99020
Go to dashboardThe Linux kernel's TPS6594 regulator driver for TPS65224 BUCK2-4 (and TPS652G1) declares four linear ranges while its table holds only two, so lookups for high selectors read beyond the array. The sources describe an out-of-bounds read during regulator registration; they do not describe code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only systems running a Linux kernel with the TPS6594 regulator driver for TPS65224 or TPS652G1 power management chips, typically embedded or hardware-specific boards. Ordinary servers and desktops without these chips are unlikely to load the driver and can skip it. The sources do not give exact affected kernel versions.
No product ranges from the sources yet.
uname -r and whether the TPS65224 or TPS652G1 regulator driver is loaded with lsmod | grep tps65Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99020")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.