CVE-2024-43830 is a use-after-free race in the Linux kernel LED trigger subsystem. LED triggers with trigger-specific sysfs attributes commonly allocate associated trigger data during their activate() callback and free it during deactivate(). The vulnerable teardown ordering invoked deactivate() before unregistering the trigger's sysfs attribute groups. Concurrent sysfs show or store operations could therefore execute after deactivation and dereference trigger data that had already been freed. The fix unregisters the sysfs groups with device_remove_groups() before invoking deactivate(), matching the reverse order of activation.
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.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.