We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2024-35824

misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume



Description

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().

Reserved 2024-05-17 | Published 2024-05-17 | Updated 2024-12-19 | Assigner Linux

Product status

Default status
unaffected

2c1164ad927e62f122b151493bb183bc11dab8f8 before 4154e767354140db7804207117e7238fb337b0e7
affected

1229ce1c4acd36f5af97c996420defc43daca635 before 997ca415384612c8df76d99d9a768e0b3f42b325
affected

755182e1e8667272a082506a2a20b4cdd78ab4c2 before f6df761182fc953907b18aba5049fc2a044ecb45
affected

b1b9f7a494400c0c39f8cd83de3aaa6111c55087 before ac3e0384073b2408d6cb0d972fee9fcc3776053d
affected

Default status
unaffected

6.1.77 before 6.1.84
affected

6.6.16 before 6.6.24
affected

6.7.4 before 6.7.12
affected

References

git.kernel.org/...c/4154e767354140db7804207117e7238fb337b0e7

git.kernel.org/...c/997ca415384612c8df76d99d9a768e0b3f42b325

git.kernel.org/...c/f6df761182fc953907b18aba5049fc2a044ecb45

git.kernel.org/...c/ac3e0384073b2408d6cb0d972fee9fcc3776053d

cve.org (CVE-2024-35824)

nvd.nist.gov (CVE-2024-35824)

Download JSON

Share this page
https://cve.threatint.com/CVE/CVE-2024-35824

Support options

Helpdesk Chat, Email, Knowledgebase
Telegram Chat
Subscribe to our newsletter to learn more about our work.