Cloudanix VulnDB

CVE-2026-99021

None

CVSS

—

EPSS

0.2%

Published

Oct 23, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A recent Linux kernel bug could cause some computers to crash when managing power supplies for hardware components.

Exploitation
Local Privilege
Attacker needs
Low Privilege
Complexity
Moderate
Impact
Data Exposure
Component
OS kernel
Class
Memory Corruption
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

of_regulator_bulk_get_all allocates a bulk regulator array but only populates consumer fields, leaving supply names uninitialized so that regulator_bulk_enable dereferences invalid memory when a supply fails to enable.

Why it matters to the business

Kernel instability or crashes may occur on affected Linux systems during power regulator initialization, potentially reducing device uptime until patched.

How an attack unfolds

An attacker with local access on a vulnerable kernel triggers device-tree-based bulk regulator acquisition followed by enable operations, causing the uninitialized name dereference and subsequent memory corruption.

How to fix it

Apply the upstream kernel commit that copies each supply name into the array allocation immediately after the entries, or update to a kernel release containing this regulator fix.

How to confirm the fix worked

Confirm the fix by inspecting the regulator/of.c source for the name-copy logic after of_regulator_bulk_get_all and by verifying that regulator_bulk_enable no longer uses a 64-byte stack buffer for names.

Typical attack path

  1. Obtain local code execution on the target system
  2. Trigger code paths that call of_regulator_bulk_get_all
  3. Invoke regulator_bulk_enable on the returned array
  4. Force a failure path that prints the uninitialized supply name

How to detect it

Search kernel logs and crash dumps for messages from regulator_bulk_enable that reference uninitialized supply names or oops traces involving of_regulator_bulk_get_all.

  • regulator_bulk_enable
  • of_regulator_bulk_get_all
  • is_supply_name

What your security team should do

  • Prioritize kernel updates on all Linux systems within normal change windows given low EPSS and absence from KEV
  • Review device-tree regulator configurations for bulk usage
  • Monitor kernel oops logs for regulator-related panics

The record

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.

Affected packages

Ecosystem Package Introduced Fixed