regulator: core: fix use_count leakage when handling boot-on
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackepss 0.1%
exploitation probability
0.1%top 96% of all CVEs
observed exploitation
nono source reports it
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.
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/0591b14ce0398125439c759f889647369aa616a0https://git.kernel.org/stable/c/4b737246ff50f810d6ab4be13c1388a07f0c14b1https://git.kernel.org/stable/c/4dd6e1cc9c7403f1ee1b7eee85bc31b797ae8347https://git.kernel.org/stable/c/5bfc53df288e8ea54ca6866fb92034214940183fhttps://git.kernel.org/stable/c/bc6c381df5793ebcf32db88a3e65acf7870379fchttps://git.kernel.org/stable/c/dc3391d49479bc2bf8a2b88dbf86fdd800882feehttps://git.kernel.org/stable/c/feb847e6591e8c7a09cc39721cc9ca74fd9a5d80