CVE-2024-35824 is an improper resource-lifecycle management flaw in the Linux kernel lis3lv02d_i2c accelerometer driver. System suspend and resume handling did not correctly account for runtime power-management state. During suspend, the driver could power off an already runtime-suspended device, resulting in a second regulator disable. For wakeup-enabled devices that were runtime-suspended, it could also fail to power the device back on for wakeup operation. During resume, the driver could power on a runtime-suspended device and subsequently power it on again during runtime resume, causing an accumulating regulator enable-count imbalance. The upstream fix makes system suspend and resume mirror the runtime-PM state and avoids redundant power transitions.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel lis3lv02d_i2c driver flaw involving regulators being enabled or disabled twice during suspend/resume.
Unknown
A Linux kernel vulnerability in the lis3lv02d_i2c misc driver involving regulators being enabled or disabled twice during suspend/resume operations.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.