---
id: "CVE-2026-99021"
kind: "vulnerability"
aliases: ["CVE-2026-99021"]
title: "Linux kernel: regulator bulk lookup leaves supply names uninitialised"
severity: "unknown"
cvss: null
epss: 0.00206
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["device-tree", "embedded", "linux-kernel", "runtime"]
not_affected_if: ["no-regulator-consumers"]
published_at: "2026-10-23T13:17:25+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99021", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99021", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# Linux kernel: regulator bulk lookup leaves supply names uninitialised

The Linux kernel's regulator bulk-get helper returned arrays whose supply name fields were never filled in, so a later error print can read uninitialised memory. The fix copies each name into the array's own allocation.

_Summary, check and fix written by a model from the sources; labelled as such._

## Fix

- Update the Linux kernel to a release that includes the upstream regulator fix for of_regulator_bulk_get_all() (version unknown from the sources).

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99021
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-99021

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

regulator: of: fill in supply names in of_regulator_bulk_get_all()

of_regulator_bulk_get_all() returns an array it allocated itself, and
fills in only the consumer of each entry. Every other way of getting a
bulk array has the supply name set, because the caller provides it, and
the core expects it to be there: regulator_bulk_enable() prints it when
a supply fails to enable, so a caller that hands such an array to it
dereferences uninitialised memory on that path.

Copy each name into the array's own allocation, right behind the
entries, so that it shares the array's lifetime and callers still have
nothing extra to free. That also retires the fixed 64 byte stack buffer
the names were assembled in, which is_supply_name() never bounded the
copy against.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_