🛡️ CVE-2024-35824 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-35824 is recorded against 2 packages.

  • kernel (from 6.7.4 up to 6.7.12)
  • linux-kernel

Timeline and source

Published on 17 May 2024 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-35824 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-05-17
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.7.4 6.7.12
linux-kernel — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-35824 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024