Live › vulnerability › CVE-2026-99021
Go to dashboardThe 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 written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Affects systems running a Linux kernel with the regulator subsystem and device-tree regulator consumers that use of_regulator_bulk_get_all(). The sources describe an uninitialised read on an error path, not a remote trigger. Systems without these drivers in use are unlikely to be exposed.
No product ranges from the sources yet.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99021")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.