VulnerabilityPublished 26 Oct 2026Updated 27 Oct 2026

CVE-2026-99020: Linux kernel · regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-99020· Low

Not known to be exploited.

Data as of 28 Oct 2026, 01:57 UTC

Severity

Low

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10linux`pkg:deb/ubuntu/linux?arch=source&distro=stonking`Other threats	Affected 7.0.0-14.14 – 7.3.0-9.9 6 affected builds	Fixed in–
Ubuntu 26.10linux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonking`Other threats	Affected =7.0.0-1004.4 =7.3.0-1002.3 =7.3.0-1003.4	Fixed in–
Ubuntu 26.10linux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that corrects the n_linear_ranges count by using ARRAY_SIZE() to match the actual size of the linear range array. Users should apply the updated Linux kernel versions that include this fix. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's tps6594 regulator driver affects the TPS65224 BUCK2, BUCK3, and BUCK4 voltage regulators. The issue arises because the driver incorrectly specifies the number of linear voltage ranges, causing out-of-bounds array access during voltage selector lookups. This flaw also impacts the TPS652G1 device. The problem has been fixed by adjusting the count of linear ranges to match the actual table size using ARRAY_SIZE().

Impact

This vulnerability can cause the kernel to read memory beyond the intended array bounds during voltage selector lookups, which may lead to incorrect voltage constraint handling. While the description does not specify exploitation consequences such as privilege escalation or denial of service, out-of-bounds reads in kernel code can potentially cause system instability or unpredictable behavior.

Summary

The Linux kernel's tps6594-regulator driver for TPS65224 BUCK2-4 descriptors incorrectly sets n_linear_ranges to 4, while the corresponding range array only contains two entries. This mismatch causes the linear range helper functions to read beyond the array bounds when processing voltage selectors above 0x45, potentially leading to incorrect voltage constraint checks. The same issue affects TPS652G1 devices using similar descriptors. The fix involves using ARRAY_SIZE() to ensure the count of linear ranges matches the actual array size, preventing out-of-bounds reads.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 01:57 UTC

Technical details

References

Community reviews

Related threats