Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4154e767354140db7804207117e7238fb337b0e7, 6.1.84, 6.6.24.

Low priority for now. Upgrade to Linux Linux 4154e767354140db7804207117e7238fb337b0e7, 6.1.84, 6.6.24 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-35824

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.1.77 and later · before 6.1.84
  • linux linux kernel6.6.16 and later · before 6.6.24
  • linux linux kernel6.7.4 and later · before 6.7.12
  • linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2c1164ad927e62f122b151493bb183bc11dab8f8 and later · before 4154e767354140db7804207117e7238fb337b0e7affected · git
    • 1229ce1c4acd36f5af97c996420defc43daca635 and later · before 997ca415384612c8df76d99d9a768e0b3f42b325affected · git
    • 755182e1e8667272a082506a2a20b4cdd78ab4c2 and later · before f6df761182fc953907b18aba5049fc2a044ecb45affected · git
    • b1b9f7a494400c0c39f8cd83de3aaa6111c55087 and later · before ac3e0384073b2408d6cb0d972fee9fcc3776053daffected · git
    • 6.1.77 and later · before 6.1.84affected · semver
    • 6.6.16 and later · before 6.6.24affected · semver
    • 6.7.4 and later · before 6.7.12affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.85-16.1.85-1
Debian:13linuxbefore 6.7.12-16.7.12-1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.55.1.el9_40:7.3.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-develbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-docbefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.55.1.el9_40:5.14.0-427.55.1.el9_4

+56

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35821May 17, 2024 · ubifs: Set page uptodate in the correct place
    22Monitor
  • ← EarlierCVE-2024-35822May 17, 2024 · usb: udc: remove warning when queue disabled ep
    22Monitor
  • Later →CVE-2024-35825May 17, 2024 · usb: gadget: ncm: Fix handling of zero block length packets
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4154e767354140db7804207117e7238fb337b0e7Vendor (CNA)
Linux Linux6.1.84Vendor (CNA)
Linux Linux6.6.24Vendor (CNA)
Linux Linux6.7.12Vendor (CNA)
Linux Linux997ca415384612c8df76d99d9a768e0b3f42b325Vendor (CNA)
Linux Linuxac3e0384073b2408d6cb0d972fee9fcc3776053dVendor (CNA)
Linux Linuxf6df761182fc953907b18aba5049fc2a044ecb45Vendor (CNA)
debian:linux6.1.85-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.55.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records