VulnerabilityPublished 26 Oct 2026Updated 27 Oct 2026

CVE-2026-99021: Linux kernel · regulator: of: fill in supply names in of_regulator_bulk_get_all()

Affects Linux kernelSource GCVE Database

Authoritative record:CVE-2026-99021· Medium

Not known to be exploited.

Data as of 28 Oct 2026, 01:57 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10linux`pkg:deb/ubuntu/linux?arch=source&distro=stonking`Other threats	Affected 7.0.0-14.14 – 7.3.0-9.9 6 affected builds	Fixed in–
Ubuntu 26.10linux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=stonking`Other threats	Affected 7.0.0-1004.4 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonking`Other threats	Affected =7.0.0-1004.4 =7.3.0-1002.3 =7.3.0-1003.4	Fixed in–
Ubuntu 26.10linux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–
Ubuntu 26.10linux-oracle`pkg:deb/ubuntu/linux-oracle?arch=source&distro=stonking`Other threats	Affected 7.0.0-1003.3 – 7.3.0-1003.3 5 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been implemented that properly initializes supply names within the array returned by of_regulator_bulk_get_all(). Users should update to patched kernel versions to resolve this issue. No additional mitigation steps are indicated.

Description

A vulnerability in the Linux kernel's regulator subsystem was fixed where the function of_regulator_bulk_get_all() did not properly initialize supply names in the returned array. This could lead to uninitialized memory dereferences when the array is used, such as during error logging in regulator_bulk_enable(). The fix involves copying supply names into the array's own allocation to ensure proper lifetime management and prevent memory issues.

Impact

Uninitialized memory dereference can occur in the Linux kernel's regulator subsystem during error handling, potentially leading to kernel instability or crashes. This affects systems using the vulnerable kernel versions when regulator_bulk_enable() is called with arrays from of_regulator_bulk_get_all(). No known exploits are reported in the wild.

Summary

The Linux kernel's function of_regulator_bulk_get_all() returns an allocated array but only initializes the consumer field of each entry, leaving supply names uninitialized. Other bulk array retrieval methods set supply names because the caller provides them, and the core expects these names to be present. The lack of initialized supply names causes regulator_bulk_enable() to dereference uninitialized memory when it attempts to print supply names upon failure to enable a supply. The patch copies each supply name into the array's allocation, sharing the array's lifetime and eliminating the use of a fixed-size stack buffer previously used for name assembly.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 01:57 UTC

Technical details

References

Community reviews

Related threats