CVE-2022-50250regulator: core: fix use_count leakage when handling boot-on
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 14 months later
· 14 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected dc1b1d7faf616ed663d0bba9be5abb4d1ed35d01 – < dc3391d49479bc2bf8a2b88dbf86fdd800882fee
- affected f44b07472f29ae313ce875dc7b9c75b100c608b8 – < 5bfc53df288e8ea54ca6866fb92034214940183f
- affected 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b – < 4b737246ff50f810d6ab4be13c1388a07f0c14b1
- affected 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b – < feb847e6591e8c7a09cc39721cc9ca74fd9a5d80
- affected 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b – < 4dd6e1cc9c7403f1ee1b7eee85bc31b797ae8347
- affected 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b – < bc6c381df5793ebcf32db88a3e65acf7870379fc
- affected 089b3f61ecfc43ca4ea26d595e1d31ead6de3f7b – < 0591b14ce0398125439c759f889647369aa616a0
- affected 4.19.226 – < 4.19.270
- affected 5.4.7 – < 5.4.229
- affected 5.5
- unaffected < 5.5
- unaffected 4.19.270 – ≤ 4.19.*
- unaffected 5.4.229 – ≤ 5.4.*
- unaffected 5.10.163 – ≤ 5.10.*
- unaffected 5.15.86 – ≤ 5.15.*
- unaffected 6.0.16 – ≤ 6.0.*
- unaffected 6.1.2 – ≤ 6.1.*
- unaffected 6.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/dc3391d49479bc2bf8a2b88dbf86fdd800882fee (opens in a new tab)
- https://git.kernel.org/stable/c/5bfc53df288e8ea54ca6866fb92034214940183f (opens in a new tab)
- https://git.kernel.org/stable/c/4b737246ff50f810d6ab4be13c1388a07f0c14b1 (opens in a new tab)
- https://git.kernel.org/stable/c/feb847e6591e8c7a09cc39721cc9ca74fd9a5d80 (opens in a new tab)
- https://git.kernel.org/stable/c/4dd6e1cc9c7403f1ee1b7eee85bc31b797ae8347 (opens in a new tab)
- https://git.kernel.org/stable/c/bc6c381df5793ebcf32db88a3e65acf7870379fc (opens in a new tab)
- https://git.kernel.org/stable/c/0591b14ce0398125439c759f889647369aa616a0 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55502 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50250)Record last updated .