GHSA-69FG-P93R-FPJ4
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-99020"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:24Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nregulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4\n\nThe TPS65224 BUCK2, BUCK3 and BUCK4 descriptors pass 4 as\nn_linear_ranges, but tps65224_bucks_2_3_4_ranges[] only has two\nentries, covering selectors 0x00-0x45.\n\nThe linear range helpers loop over n_linear_ranges entries, so any\nlookup of a selector above 0x45 reads past the end of the array and\ntreats whatever follows it as two more ranges. This happens on the\nnormal registration path when the core checks the voltage constraints\nagainst every selector. TPS652G1 uses the same descriptors and is\naffected too.\n\nUse ARRAY_SIZE() so the count always matches the table.",
"id": "GHSA-69fg-p93r-fpj4",
"modified": "2026-10-23T15:31:35Z",
"published": "2026-10-23T15:31:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99020"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1ea151615a82fd94f25e38b2cc7eeac49112508b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2f15518682c779b1014552cb2ccb4a2052f85f27"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/66b7da589b2ce44a02b8387c6160e9254685f34f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f3423b56be12208a393274afb9a5e3d67fc58ce3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f6fbe9c6b39968a7696b9badef4bc29331a6376a"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.