Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Authoritative record:CVE-2026-99020· Low

Not known to be exploited · fixed in f3423b56be12208a393274afb9a5e3d67fc58ce3 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity
Low

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f3423b56be12208a393274afb9a5e3d67fc58ce3, f6fbe9c6b39968a7696b9badef4bc29331a6376a, 66b7da589b2ce44a02b8387c6160e9254685f34f +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.6.157 <6.6.160
Fixed in
  • f3423b56be12208a393274afb9a5e3d67fc58ce3
  • f6fbe9c6b39968a7696b9badef4bc29331a6376a
  • 66b7da589b2ce44a02b8387c6160e9254685f34f
  • 6.6.160
  • 2f15518682c779b1014552cb2ccb4a2052f85f27
  • 1ea151615a82fd94f25e38b2cc7eeac49112508b
LinuxLinuxAffected
  • =6.10
Fixed in–

Description

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.

References

Community reviews

Loading reviews…