Loading vulnerability…
CVE-2024-38615 is a flaw in the Linux kernel cpufreq subsystem's handling of driver teardown. The cpufreq exit() callback is optional, but vulnerable code can invoke it without validating that the callback pointer is present. In addition, the frequency-table pointer may remain uncleared when no exit() callback exists. The flaw can result in a null-pointer dereference and availability impact.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel CPU frequency-scaling (cpufreq) flaw in which an optional exit() callback could be called without validating its function pointer, potentially causing a local denial of service through system availability impact.
Linux CPU frequency subsystem mishandles an optional exit callback.
Linux kernel CPU frequency-management flaw concerning optional exit callbacks.
Linux kernel CPU-frequency subsystem flaw concerning the optional exit callback.
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.