CVE-2024-26603 is a denial-of-service vulnerability in the Linux kernel x86 FPU signal-frame restore path. The code used the userspace-controlled xstate_size field in the XSAVE signal-frame software-reserved area to determine how much of the FPU buffer to fault in before executing XRSTOR. A local process can construct a sigreturn frame whose xstate_size is smaller than the state implied by its xfeatures bits, then unmap the portion of the FPU buffer that XRSTOR will subsequently access. The preliminary readability check succeeds for the attacker-supplied shorter size, but XRSTOR faults on the unmapped portion. Retrying this sequence causes an infinite fault-handling loop. The fix faults in the maximum buffer size XRSTOR may access, using the kernel-maintained fpstate user_size rather than userspace metadata.
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 x86 FPU/XSAVE handling flaw that can cause an endless loop.
Linux kernel x86 FPU flaw that could cause an endless loop while faulting in an XSAVE buffer.
Linux kernel x86 FPU XSAVE-buffer handling flaw that can cause an endless loop.
Linux kernel x86 FPU handling issue that can result in an infinite loop while faulting in an XSAVE buffer.
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.