Loading vulnerability…
CVE-2024-50275 is a race condition in the Linux kernel arm64 Scalable Vector Extension (SVE) trap handler. Incorrect handling of saved FPSIMD/SVE state during preemption and CPU migration can leave TIF_SVE set and TIF_FOREIGN_FPSTATE clear even though the live CPU state is stale. If the task returns to its original CPU while still associated with that CPU's saved state, the kernel can reuse stale hardware state and return to userspace without restoring the correct FPSIMD/SVE state from memory.
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.
A Linux kernel ARM64 Scalable Vector Extension (SVE) vulnerability related to stale CPU state during SVE trap handling, fixed in the Rocky Linux 8 CRLSA-2025_1067 update.
A Linux kernel arm64 Scalable Vector Extension (SVE) state-handling race condition. During SVE trap handling, preemption and CPU migration can leave thread flags inconsistent and allow stale hardware FPSIMD/SVE state to be reused, potentially affecting confidentiality, integrity, and availability.
Linux kernel ARM64 SVE stale CPU-state handling flaw during SVE traps.
A Linux kernel ARM64 Scalable Vector Extension (SVE) issue involving stale CPU state during SVE trap handling.
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.