Loading vulnerability…
CVE-2023-52635 is a race condition in the Linux kernel PM/devfreq subsystem. Concurrent or rapidly alternating devfreq governor changes can cause devfreq_monitor_start() and devfreq_monitor_stop() to unsafely queue, execute, cancel, or reinitialize the same delayed-work timer. Competing timer cancellation and expiration operations can corrupt timer-list or delayed-work state, resulting in a kernel paging fault during timer expiration. The upstream fix synchronizes monitor start and stop operations using the polling flag and the devfreq lock.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel devfreq monitor start/stop synchronization issue.
Linux kernel devfreq power-management synchronization flaw in monitor start/stop operations.
Linux kernel power-management/devfreq synchronization flaw affecting devfreq monitor start and stop operations.
A vulnerability remediated by the OpenShift Container Platform 4.14.35 security update; no technical description is provided.
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.