VulnerabilityPublished 23 Oct 2026

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

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in e2151c29cec73f6cc70abf1c7cbc7b9b202489f5 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:30 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in e2151c29cec73f6cc70abf1c7cbc7b9b202489f5, a3384ec2516a7cc567bd7c09029282494469b247, 82ac8c4939bdbd064b4f54a580fbe4baf0d60e41 +1

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

Upgrade Linux kernel to e2151c29cec73f6cc70abf1c7cbc7b9b202489f5, a3384ec2516a7cc567bd7c09029282494469b247, 82ac8c4939bdbd064b4f54a580fbe4baf0d60e41 or 6.2.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected >=6.1.110 <6.2	Fixed in e2151c29cec73f6cc70abf1c7cbc7b9b202489f5 a3384ec2516a7cc567bd7c09029282494469b247 82ac8c4939bdbd064b4f54a580fbe4baf0d60e41 6.2
LinuxLinux	Affected =6.2	Fixed in–

AI-suggested

This vulnerability has been fixed in Linux kernel version 6.2 and specific commits (e2151c29cec73f6cc70abf1c7cbc7b9b202489f5, a3384ec2516a7cc567bd7c09029282494469b247, 82ac8c4939bdbd064b4f54a580fbe4baf0d60e41). Users and administrators should upgrade to Linux kernel 6.2 or later to resolve this issue. No additional mitigation is required beyond applying the official fix.

Description

A vulnerability in the Linux kernel's regulator subsystem was fixed by ensuring supply names are properly filled in the of_regulator_bulk_get_all() function. Previously, this function returned an array with uninitialized supply name fields, leading to potential dereferencing of uninitialized memory when the array was used by regulator_bulk_enable(). The fix copies each supply name into the array's allocation to ensure proper memory handling and prevent use of uninitialized data.

Impact

The vulnerability could lead to dereferencing uninitialized memory in the Linux kernel regulator subsystem, potentially causing kernel crashes or undefined behavior when regulator_bulk_enable() attempts to print a supply name that was never initialized. This impacts kernel stability and reliability but there is no indication of direct code execution or privilege escalation from the provided data.

Summary

The Linux kernel's of_regulator_bulk_get_all() function allocated and returned an array but only initialized the consumer field of each entry, leaving supply name fields uninitialized. Other bulk array retrieval methods set the supply name because the caller provides it, and the core expects it to be present. regulator_bulk_enable() prints the supply name when enabling a supply fails, which caused it to dereference uninitialized memory if the supply name was missing. The patch copies each supply name into the array's own allocation, sharing the array's lifetime and eliminating the use of a fixed-size stack buffer that was previously used unsafely.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:57 UTC

Technical details

References

Community reviews

Related threats