misc: lis3lv02d_i2c: Fix regulators getting en-/dis-abled twice on suspend/resume
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 997ca415384612c8df76d99d9a768e0b3f42b325, Kernel 4154e767354140db7804207117e7238fb337b0e7, Kernel 6.1.84 and 4 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=1229ce1c4acd36f5af97c996420defc43daca635 <997ca415384612c8df76d99d9a768e0b3f42b325, >=2c1164ad927e62f122b151493bb183bc11dab8f8 <4154e767354140db7804207117e7238fb337b0e7, >=6.1.77 <6.1.84, >=6.6.16 <6.6.24, >=6.7.4 <6.7.12, >=755182e1e8667272a082506a2a20b4cdd78ab4c2 <f6df761182fc953907b18aba5049fc2a044ecb45, >=b1b9f7a494400c0c39f8cd83de3aaa6111c55087 <ac3e0384073b2408d6cb0d972fee9fcc3776053d | 997ca415384612c8df76d99d9a768e0b3f42b325, 4154e767354140db7804207117e7238fb337b0e7, 6.1.84, 6.6.24, 6.7.12, f6df761182fc953907b18aba5049fc2a044ecb45, ac3e0384073b2408d6cb0d972fee9fcc3776053d |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket