Loading vulnerability…
CVE-2024-35809 is a race condition in the Linux kernel PCI power-management removal path. During PCI driver removal, pci_device_remove() invokes pm_runtime_get_sync(), but that operation does not wait for an already executing .runtime_idle() callback. Consequently, a runtime-idle callback can continue concurrently with driver teardown. This was observed in the rtsx_pcr PCI driver, where the concurrency leads to an unhandled page fault and kernel crash. The upstream fix invokes pm_runtime_barrier() after pm_runtime_get_sync() in pci_device_remove(), while the runtime PM usage count prevents new runtime-PM callbacks, thereby draining an in-progress runtime-idle callback before driver removal proceeds.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel PCI power-management flaw involving runtime-idle callbacks during driver removal.
A Linux kernel PCI power-management vulnerability involving runtime-idle callbacks during driver removal. The issue was resolved by draining runtime-idle callbacks before removing the driver.
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.