LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22008: regulator: check that dummy regulator has been probed before using it

In the Linux kernel, the following vulnerability has been resolved: regulator: check that dummy regulator has been probed before using it Due to asynchronous driver probing there is a chance that the dummy regulator hasn't already been probed when first accessing it.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel flaw in regulator initialization. A built-in dummy regulator might be used before its driver has finished probing, creating unreliable behavior during device startup. The public sources do not state business impact, CVSS, or confirmed exploitation.

Executive priority

Treat this as a kernel maintenance item with uncertain severity. Prioritize patching where affected kernels run on production, embedded, or appliance systems, but do not escalate as actively exploited based on the provided evidence.

Technical view

CVE-2025-22008 affects the Linux kernel regulator subsystem. Because driver probing can be asynchronous, code may access the dummy regulator before it has been probed. Kernel stable commits resolve this by checking that the dummy regulator has been probed before use.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or downstream kernels carrying the vulnerable regulator code. The bundle names Linux 6.4 and later affected ranges, with Debian LTS advisories also referencing fixes.

Exploitation context

The source bundle does not identify active exploitation, public exploit availability, attacker prerequisites, or a clear impact class. It is not listed as CISA KEV in the provided data.

Researcher notes

Evidence is thin: no CVSS, CWE, exploit narrative, or impact statement is provided. Analysis should focus on affected kernel lineage, whether the stable commits are present, and vendor backport status.

Mitigation direction

  • Apply Linux kernel updates that include the referenced stable fixes.
  • For Debian LTS systems, apply the relevant Debian security updates.
  • Check your Linux vendor advisory for backported fixes.
  • Prioritize embedded or hardware-dependent Linux systems using regulator framework paths.

Validation and detection

  • Inventory running kernel versions across Linux hosts and appliances.
  • Compare deployed kernels against vendor fixed package versions.
  • Check whether downstream kernels include the referenced stable commits.
  • Review boot and driver initialization logs for regulator-related failures.
Prepared
Confidence
medium
Sources
8

Public sources used

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.

cve · low confidence lookup

CVE-2025-22008 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
1ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux259b93b21a9ffe5117af4dfb5505437e463c6a5a, 259b93b21a9ffe5117af4dfb5505437e463c6a5a, 259b93b21a9ffe5117af4dfb5505437e463c6a5a, 259b93b21a9ffe5117af4dfb5505437e463c6a5aunaffected
LinuxLinux6.4, 0, 6.6.85, 6.12.21, 6.13.9, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.