# CVE-2026-99021: regulator: of: fill in supply names in of_regulator_bulk_get_all()


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110870, BELL-CVE-2026-99021, DEBIAN-CVE-2026-99021, GHSA-pp3v-c45m-5x73, UBUNTU-CVE-2026-99021

## What is CVE-2026-99021?

CVE-2026-99021 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

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.

## Which versions are affected by CVE-2026-99021?


## How do I fix CVE-2026-99021?

Upgrade to a fixed version.

## Is CVE-2026-99021 being exploited?

There is no known exploitation of CVE-2026-99021 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99021 and fix it if it is affected.

What it is: CVE-2026-99021 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99021 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99021/ (Markdown: https://insights.sbomify.com/CVE-2026-99021/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99021
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99021
- OSV: https://osv.dev/vulnerability/CVE-2026-99021

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99021/
Summaries are generated and may contain mistakes; the official description above is the record.