CVE-2024-35824
published 2024-05-17CVE-2024-35824: In the Linux kernel, the following vulnerability has been resolved: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume When not…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
When not configured for wakeup lis3lv02d_i2c_suspend() will call
lis3lv02d_poweroff() even if the device has already been turned off
by the runtime-suspend handler and if configured for wakeup and
the device is runtime-suspended at this point then it is not turned
back on to serve as a wakeup source.
Before commit b1b9f7a49440 ("misc: lis3lv02d_i2c: Add missing setting
of the reg_ctrl callback"), lis3lv02d_poweroff() failed to disable
the regulators which as a side effect made calling poweroff() twice ok.
Now that poweroff() correctly disables the regulators, doing this twice
triggers a WARN() in the regulator core:
unbalanced disables for regulator-dummy
WARNING: CPU: 1 PID: 92 at drivers/regulator/core.c:2999 _regulator_disable
...
Fix lis3lv02d_i2c_suspend() to not call poweroff() a second time if
already runtime-suspended and add a poweron() call when necessary to
make wakeup work.
lis3lv02d_i2c_resume() has similar issues, with an added weirness that
it always powers on the device if it is runtime suspended, after which
the first runtime-resume will call poweron() again, causing the enabled
count for the regulator to increase by 1 every suspend/resume. These
unbalanced regulator_enable() calls cause the regulator to never
be turned off and trigger the following WARN() on driver unbind:
WARNING: CPU: 1 PID: 1724 at drivers/regulator/core.c:2396 _regulator_put
Fix this by making lis3lv02d_i2c_resume() mirror the new suspend().
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.85-1 (bookworm) | linux 6.1.85-1 (bookworm) |
| linux | linux | >= 1229ce1c4acd36f5af97c996420defc43daca635 < 997ca415384612c8df76d99d9a768e0b3f42b325 | 997ca415384612c8df76d99d9a768e0b3f42b325 |
| linux | linux | >= 2c1164ad927e62f122b151493bb183bc11dab8f8 < 4154e767354140db7804207117e7238fb337b0e7 | 4154e767354140db7804207117e7238fb337b0e7 |
| linux | linux | >= 6.1.77 < 6.1.84 | 6.1.84 |
| linux | linux | >= 6.6.16 < 6.6.24 | 6.6.24 |
| linux | linux | >= 6.7.4 < 6.7.12 | 6.7.12 |
| linux | linux | >= 755182e1e8667272a082506a2a20b4cdd78ab4c2 < f6df761182fc953907b18aba5049fc2a044ecb45 | f6df761182fc953907b18aba5049fc2a044ecb45 |
| linux | linux | >= b1b9f7a494400c0c39f8cd83de3aaa6111c55087 < ac3e0384073b2408d6cb0d972fee9fcc3776053d | ac3e0384073b2408d6cb0d972fee9fcc3776053d |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.1.85-1 | 6.1.85-1 |
| linux | linux_kernel | >= 0 < 6.7.12-1 | 6.7.12-1 |
| linux | linux_kernel | >= 0 < 6.7.12-1 | 6.7.12-1 |
| linux | linux_kernel | >= 6.1.77 < 6.1.84 | 6.1.84 |
| linux | linux_kernel | >= 6.6.16 < 6.6.24 | 6.6.24 |
| linux | linux_kernel | >= 6.7.4 < 6.7.12 | 6.7.12 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-wwvg-j77r-54mx: In the Linux kernel, the following vulnerability has been resolved:
misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
ghsa_unreviewed·2024-05-17
CVE-2024-35824 [MEDIUM] GHSA-wwvg-j77r-54mx: In the Linux kernel, the following vulnerability has been resolved:
misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
In the Linux kernel, the following vulnerability has been resolved:
misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
When not configured for wakeup lis3lv02d_i2c_suspend() will call
lis3lv02d_poweroff() even if the device has already been turned off
by the runtime-suspend handler and if configured for wakeup and
the device is runtime-suspended at this point then it is not turned
back on to serve as a wakeup source.
Before commit b1b9f7a49440 ("misc: lis3lv02d_i2c: Add missing setting
of the reg_ctrl callback"), lis3lv02d_poweroff() failed to disable
the regulators which as a side effect made calling poweroff() twice ok.
Now that poweroff() correctly disables the regulators, doing this twice
triggers a WARN() in the regulator core:
unbalanced disables f
OSV
CVE-2024-35824: In the Linux kernel, the following vulnerability has been resolved: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
osv·2024-05-17·CVSS 5.5
CVE-2024-35824 [MEDIUM] CVE-2024-35824: In the Linux kernel, the following vulnerability has been resolved: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
In the Linux kernel, the following vulnerability has been resolved: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume When not configured for wakeup lis3lv02d_i2c_suspend() will call lis3lv02d_poweroff() even if the device has already been turned off by the runtime-suspend handler and if configured for wakeup and the device is runtime-suspended at this point then it is not turned back on to serve as a wakeup source. Before commit b1b9f7a49440 ("misc: lis3lv02d_i2c: Add missing setting of the reg_ctrl callback"), lis3lv02d_poweroff() failed to disable the regulators which as a side effect made calling poweroff() twice ok. Now that poweroff() correctly disables the regulators, doing this twice triggers a WARN() in the regulator core: unbalanced disables for re
Red Hat
kernel: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
vendor_redhat·2024-05-17·CVSS 5.5
CVE-2024-35824 [MEDIUM] kernel: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
kernel: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
In the Linux kernel, the following vulnerability has been resolved:
misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
When not configured for wakeup lis3lv02d_i2c_suspend() will call
lis3lv02d_poweroff() even if the device has already been turned off
by the runtime-suspend handler and if configured for wakeup and
the device is runtime-suspended at this point then it is not turned
back on to serve as a wakeup source.
Before commit b1b9f7a49440 ("misc: lis3lv02d_i2c: Add missing setting
of the reg_ctrl callback"), lis3lv02d_poweroff() failed to disable
the regulators which as a side effect made calling poweroff() twice ok.
Now that poweroff() correctly disables the regul
Debian
CVE-2024-35824: linux - In the Linux kernel, the following vulnerability has been resolved: misc: lis3l...
vendor_debian·2024·CVSS 5.5
CVE-2024-35824 [MEDIUM] CVE-2024-35824: linux - In the Linux kernel, the following vulnerability has been resolved: misc: lis3l...
In the Linux kernel, the following vulnerability has been resolved: misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume When not configured for wakeup lis3lv02d_i2c_suspend() will call lis3lv02d_poweroff() even if the device has already been turned off by the runtime-suspend handler and if configured for wakeup and the device is runtime-suspended at this point then it is not turned back on to serve as a wakeup source. Before commit b1b9f7a49440 ("misc: lis3lv02d_i2c: Add missing setting of the reg_ctrl callback"), lis3lv02d_poweroff() failed to disable the regulators which as a side effect made calling poweroff() twice ok. Now that poweroff() correctly disables the regulators, doing this twice triggers a WARN() in the regulator core: unbalanced disables for re
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/4154e767354140db7804207117e7238fb337b0e7https://git.kernel.org/stable/c/997ca415384612c8df76d99d9a768e0b3f42b325https://git.kernel.org/stable/c/ac3e0384073b2408d6cb0d972fee9fcc3776053dhttps://git.kernel.org/stable/c/f6df761182fc953907b18aba5049fc2a044ecb45https://git.kernel.org/stable/c/4154e767354140db7804207117e7238fb337b0e7https://git.kernel.org/stable/c/997ca415384612c8df76d99d9a768e0b3f42b325https://git.kernel.org/stable/c/ac3e0384073b2408d6cb0d972fee9fcc3776053dhttps://git.kernel.org/stable/c/f6df761182fc953907b18aba5049fc2a044ecb45
2024-05-17
Published