Quick answers
- Is CVE-2026-99020 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-99020 being exploited in the wild.
- How severe is CVE-2026-99020?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- Unknown Linux kernel affected versions unspecified; fix included in mainline and stable trees.
- Is there a fix for CVE-2026-99020?
- A patch was published on 2026-09-30: upstream patch committed Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-99020 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-99020?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The tps6594-regulator driver specifies n_linear_ranges=4 for BUCK2, BUCK3, and BUCK4 regulators on TPS65224 and TPS652G1 PMICs, but the tps65224_bucks_2_3_4_ranges[] array contains only 2 entries. Linear range lookup code iterates over all n_linear_ranges entries without bounds checking, causing reads past the array end when voltage selectors exceed 0x45. This occurs during normal regulator registration when the kernel validates voltage constraints. The fix uses ARRAY_SIZE() to ensure the count matches the actual array size.
Affected products
- <unknown> Linux Kernel affected versions unspecified; fix included in mainline and stable trees
Timeline
- 2026-10-23: disclosed
- 2026-09-30: patched: upstream patch committed