LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50250: regulator: core: fix use_count leakage when handling boot-on

In the Linux kernel, the following vulnerability has been resolved: regulator: core: fix use_count leakage when handling boot-on I found a use_count leakage towards supply regulator of rdev with boot-on option. ┌───────────────────┐ ┌───────────────────┐ │ regulator_dev A │ │ regulator_dev B │ │ (boot-on) │ │ (boot-on) │ │ use_count=0 │◀──supply──│ use_count=1 │ │ │ │ │ └───────────────────┘ └───────────────────┘ In case of rdev(A) configured with `regulator-boot-on', the use_count of supplying regulator(B) will increment inside regulator_enable(rdev->supply). Thus, B will acts like always-on, and further balanced regulator_enable/disable cannot actually disable it anymore. However, B was also configured with `regulator-boot-on', we wish it could be disabled afterwards.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50250 is a Linux kernel regulator bug where certain boot-time power regulator settings can leave a supply regulator counted as still in use. That can prevent normal disable logic from turning it off later. The sources do not provide CVSS severity, known attack paths, or evidence of active exploitation.

Executive priority

Schedule remediation through normal kernel maintenance unless affected devices have critical power-control reliability requirements. Escalate priority for embedded, appliance, or operational systems where incorrect regulator disable behavior could affect availability, power use, or hardware behavior.

Technical view

The issue is in Linux kernel regulator core handling of regulator-boot-on. Enabling a boot-on regulator can increment the use_count of its supply regulator and fail to balance it, making the supply behave like always-on even after later balanced enable/disable operations should permit disabling.

Likely exposure

Exposure appears limited to Linux kernels in the affected version range or listed vulnerable revisions where regulator-boot-on is used with a supply regulator relationship. This is most relevant to systems depending on kernel regulator power management. The bundle does not identify distributions, device models, or package-level status.

Exploitation context

The source bundle does not cite public exploitation, KEV listing, exploit code, or remote attackability. The described impact is incorrect regulator state management. Treat exploitation context as incomplete unless a vendor or distribution advisory adds threat details.

Researcher notes

Evidence supports a regulator use_count leak fixed by upstream stable commits. Missing data includes CVSS, CWE, exploitability, privileges required, and distribution package status. Validation should focus on kernel ancestry, backports, and regulator topology rather than generic Linux presence alone.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize systems using regulator-boot-on in device-tree or board power definitions.
  • Check Linux distribution advisories for backported fixed kernel packages.
  • Avoid direct deployment assumptions from upstream versions alone.

Validation and detection

  • Inventory Linux kernel versions and downstream vendor kernel build identifiers.
  • Review board or device-tree configuration for regulator-boot-on supply relationships.
  • Confirm whether the referenced stable commits are present or backported.
  • Run regression tests for power sequencing on affected hardware.
Prepared
Confidence
medium
Sources
9

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-2022-50250 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
0ADP providers
8Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxdc1b1d7faf616ed663d0bba9be5abb4d1ed35d01, f44b07472f29ae313ce875dc7b9c75b100c608b8, 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b, 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b, 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b, 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b, 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7bunaffected
LinuxLinux5.5, 0, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

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