CVE-2025-22009: regulator: dummy: force synchronous probing
In the Linux kernel, the following vulnerability has been resolved:
regulator: dummy: force synchronous probing
Sometimes I get a NULL pointer dereference at boot time in kobject_get()
with the following call stack:
anatop_regulator_probe()
devm_regulator_register()
regulator_register()
regulator_resolve_supply()
kobject_get()
By placing some extra BUG_ON() statements I could verify that this is
raised because probing of the 'dummy' regulator driver is not completed
('dummy_regulator_rdev' is still NULL).
In the JTAG debugger I can see that dummy_regulator_probe() and
anatop_regulator_probe() can be run by different kernel threads
(kworker/u4:*). I haven't further investigated whether this can be
changed or if there are other possibilities to force synchronization
between these two probe routines. On the other hand I don't expect much
boot time penalty by probing the 'dummy' regulator synchronously.
Security readout for executives and security teams
Plain-English summary
CVE-2025-22009 is a Linux kernel availability issue. A race during boot can leave the dummy regulator uninitialized, causing a NULL pointer dereference and potentially crashing the system. The sources do not indicate data theft, privilege escalation, remote attack, or active exploitation.
Executive priority
Treat this as a moderate operational reliability risk, not a broad compromise scenario. Prioritize patch planning for Linux systems where boot failures could affect service availability or recovery objectives.
Technical view
The issue is CWE-476 in Linux regulator probing. Asynchronous probing can let anatop_regulator_probe() resolve supply before dummy_regulator_probe() finishes, leaving dummy_regulator_rdev NULL and triggering kobject_get() failure. The resolved change forces dummy regulator probing to be synchronous.
Likely exposure
Exposure is most likely on systems running the affected Linux kernel versions listed in the CVE record and using the impacted regulator path. The source bundle does not identify affected distributions, devices, or package names.
Exploitation context
The CVSS vector is local with low privileges and no user interaction, with high availability impact only. KEV is false, and the provided sources do not report active exploitation or a public exploit.
Researcher notes
Evidence points to a boot-time race in kernel driver probing, fixed by synchronous probing. The public bundle does not provide exploit details, distro mappings, or confirmation that all listed version ranges are equally reachable in practice.
Mitigation direction
Check vendor kernel advisories for CVE-2025-22009 applicability.
Update to a kernel build containing the referenced stable fixes.
Prioritize systems where reboot reliability is operationally important.
Test patched kernels in staging before production rollout.
Validation and detection
Compare deployed kernel versions against vendor guidance and the CVE record.
Confirm the running build includes the relevant stable kernel fix.
Review boot logs for NULL pointer dereference in kobject_get() or regulator paths.
Perform controlled reboot testing on representative affected hardware.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.