LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35824: 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().

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel availability issue in a sensor driver’s suspend and resume handling. Under affected conditions, the driver can imbalance power regulator enable and disable calls, triggering kernel warnings and potentially disrupting system availability. It is not described as a data theft or privilege escalation issue in the supplied sources.

Executive priority

Treat this as a targeted availability maintenance issue, not an emergency internet-facing exposure. Patch through normal kernel update channels, prioritizing fleets where suspend/resume reliability matters or where affected sensor hardware is present.

Technical view

CVE-2024-35824 affects the Linux lis3lv02d_i2c driver. Runtime suspend and system suspend/resume paths could call poweroff or poweron twice, creating unbalanced regulator state. The kernel fix changes suspend and resume behavior so runtime-suspended devices are handled correctly and wakeup behavior is preserved.

Likely exposure

Exposure appears limited to Linux systems using the lis3lv02d_i2c driver and affected kernel code paths. The supplied bundle does not provide complete distribution-specific affected ranges, so vulnerability managers should verify kernel versions and backported fixes with their Linux vendor.

Exploitation context

The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact. The bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization.

Researcher notes

The sources describe a correctness bug in regulator lifecycle handling after an earlier callback fix changed poweroff behavior. Evidence is strongest for root cause and upstream remediation. Distribution impact, exploitability beyond local availability disruption, and exact affected package ranges require vendor confirmation.

Mitigation direction

  • Apply Linux vendor kernel updates containing the referenced stable fixes.
  • Check distribution advisories for exact affected and fixed package versions.
  • Prioritize systems using lis3lv02d_i2c or related accelerometer hardware.
  • If updates are unavailable, follow vendor guidance for temporary risk reduction.
  • Track kernel warnings involving regulator enable or disable imbalance.

Validation and detection

  • Inventory Linux kernel versions across laptops, embedded systems, and appliances.
  • Confirm whether lis3lv02d_i2c is built, loaded, or used on target systems.
  • Compare installed kernels with vendor advisories and stable fix backports.
  • Review logs for regulator WARN messages during suspend, resume, or driver unbind.
  • Validate remediation by retesting suspend and resume on representative hardware.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-35824 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2024-35824Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2c1164ad927e62f122b151493bb183bc11dab8f8, 1229ce1c4acd36f5af97c996420defc43daca635, 755182e1e8667272a082506a2a20b4cdd78ab4c2, b1b9f7a494400c0c39f8cd83de3aaa6111c55087unaffected
LinuxLinux6.1.77, 6.6.16, 6.7.4unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.