Not ratedCVE-2026-99020

Linux Kernel: security vulnerability (CVE-2026-99020)

Published 23.10.2026Last modified 23.10.2026Sources: BSI, CVE.org

What is affected, what to do

Update Linux Kernel to version 6.6.160, Linux Kernel to version 6.12.113, Linux Kernel to version 6.18.57.

Affected: Linux Kernel lt 6.6.157..6.6.160
Linux Kernel lt 6.10..6.12.113
Linux Kernel lt 6.13..6.18.57
Linux Kernel lt 6.19..7.2.11
Fixed in: Linux Kernel 6.6.160
Linux Kernel 6.12.113
Linux Kernel 6.18.57
Linux Kernel 7.2.11
Linux Kernel 7.3

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

—

Priority

No value is available for this vulnerability.

—

CVSS v3

No value is available for this vulnerability.

0.2 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 6.1

Show all metrics

Severity: Not rated
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 30.30 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: no public PoC known
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 0.2 %; Low — model estimates < 1% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 6.1; Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 23.10.2026

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

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.

Source: BSI CSAF, BSI WID Portal, cvelistv5, NVD (NIST)

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
Linux	Linux	`6.19 – < 7.2.11` `6.6.157 – < 6.6.160` `—` `6.10 – < 6.12.113` `6.13 – < 6.18.57`	`7.2.11` `6.6.160` `7.3` `6.12.113` `6.18.57`

Vendors and products

Linux Linux

References & sources

git.kernel.orgstable/c/1ea151615a82fd94f25e38b2cc7eeac49112508b
git.kernel.orgstable/c/2f15518682c779b1014552cb2ccb4a2052f85f27
git.kernel.orgstable/c/66b7da589b2ce44a02b8387c6160e9254685f34f
git.kernel.orgstable/c/f3423b56be12208a393274afb9a5e3d67fc58ce3
git.kernel.orgstable/c/f6fbe9c6b39968a7696b9badef4bc29331a6376a

Changes to this CVE

Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

23.10.2026ReceivedLinux

Description added or changed

New references:

and 1 more reference

Show 7 original changes

Individual changes of this event as published by NVD
Type	Action	Before	After
Description	added	—	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.
Affected versions (publisher)	added	—	New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/99xxx/CVE-2026-99020.json">CVE-2026-99020</a>
Reference	added	—	https://git.kernel.org/stable/c/1ea151615a82fd94f25e38b2cc7eeac49112508b
Reference	added	—	https://git.kernel.org/stable/c/2f15518682c779b1014552cb2ccb4a2052f85f27
Reference	added	—	https://git.kernel.org/stable/c/66b7da589b2ce44a02b8387c6160e9254685f34f
Reference	added	—	https://git.kernel.org/stable/c/f3423b56be12208a393274afb9a5e3d67fc58ce3
Reference	added	—	https://git.kernel.org/stable/c/f6fbe9c6b39968a7696b9badef4bc29331a6376a

Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2026-99020"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-99020.svg?lang=en" alt="CVE-2026-99020 – NEOSEC Intel" height="20"></a>