CVE-2026-99020 json
regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4
published 19d ago modified 19d ago also EUVD-2026-108814
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 6.6.160, 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-99020
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99020
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/1ea151615a82fd94f25e38b2cc7eeac49112508b commit
- git.kernel.org/stable/c/66b7da589b2ce44a02b8387c6160e9254685f34f commit
- git.kernel.org/stable/c/f6fbe9c6b39968a7696b9badef4bc29331a6376a commit
- git.kernel.org/stable/c/f3423b56be12208a393274afb9a5e3d67fc58ce3 commit
- git.kernel.org/stable/c/2f15518682c779b1014552cb2ccb4a2052f85f27 commit
Is CVE-2026-99020 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99020 updated cvss 4.4
kernel: kernel: Denial of Service via out-of-bounds read in TPS6594 regulator driver
-
Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-10affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/1ea151615a82fd94f25e38b2cc7eeac49112508b
- git.kernel.org /stable/c/66b7da589b2ce44a02b8387c6160e9254685f34f
- git.kernel.org /stable/c/f6fbe9c6b39968a7696b9badef4bc29331a6376a
- git.kernel.org /stable/c/f3423b56be12208a393274afb9a5e3d67fc58ce3
- git.kernel.org /stable/c/2f15518682c779b1014552cb2ccb4a2052f85f27
Sources
- CVE List CVE-2026-99020
- NVD CVE-2026-99020
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.