# CVE-2026-99020: regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-99020, DEBIAN-CVE-2026-99020, GHSA-69fg-p93r-fpj4, UBUNTU-CVE-2026-99020

## What is CVE-2026-99020?

CVE-2026-99020 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-99020?


## How do I fix CVE-2026-99020?

Upgrade to a fixed version.

## Is CVE-2026-99020 being exploited?

There is no known exploitation of CVE-2026-99020 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99020 and fix it if it is affected.

What it is: CVE-2026-99020 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99020 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99020/ (Markdown: https://insights.sbomify.com/CVE-2026-99020/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99020
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99020
- OSV: https://osv.dev/vulnerability/CVE-2026-99020

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99020/
Summaries are generated and may contain mistakes; the official description above is the record.