regulator: core: fix use_count leakage when handling boot-on
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.19.270, 5.4.229
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4.19.226 · fixed in 4.19.270; From 5.4.7 · fixed in 5.4.229
- Linux Linux
5.5
References 7
git.kernel.org
- stable/c/dc3391d49479bc2bf8a2b88dbf86fdd800882fee
- stable/c/5bfc53df288e8ea54ca6866fb92034214940183f
- stable/c/4b737246ff50f810d6ab4be13c1388a07f0c14b1
- stable/c/feb847e6591e8c7a09cc39721cc9ca74fd9a5d80
- stable/c/4dd6e1cc9c7403f1ee1b7eee85bc31b797ae8347
- stable/c/bc6c381df5793ebcf32db88a3e65acf7870379fc
- stable/c/0591b14ce0398125439c759f889647369aa616a0