CVE-2024-35801 is a Linux kernel x86 FPU handling vulnerability caused by improper synchronization between the per-CPU cached xfd_state value and the hardware MSR_IA32_XFD register. During CPU hotplug, MSR_IA32_XFD is reset to the initial FPU-state XFD value, but the cached per-CPU xfd_state was not reset. A later xfd_update_state() operation can therefore incorrectly conclude that no MSR write is necessary. The stale hardware XFD configuration can cause an XRSTOR instruction executed in kernel context to raise a device-not-available (#NM) exception and crash the kernel.
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 x86 FPU state synchronization issue involving xfd_state and MSR_IA32_XFD.
Linux kernel x86 FPU state-management flaw in which xfd_state can fall out of synchronization with the MSR_IA32_XFD register.
A low-severity Linux kernel x86 FPU-state synchronization vulnerability concerning xfd_state and the MSR_IA32_XFD register.
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.