Loading vulnerability…
CVE-2022-50425 is a flaw in the Linux kernel x86 FPU extended-state export path, specifically copy_xstate_to_uabi(). When an extended state component is absent from an fpstate but considered to be in its initial state, the function may attempt to copy that component from init_fpstate. Dynamic XSAVE components have all-zero initial states and are not present in init_fpstate, causing an invalid source pointer to reach the copy operation and triggering a kernel NULL pointer dereference. The corrective change zeros the userspace output buffer for features unavailable in both fpstate and init_fpstate, and verifies that compacted XSAVE is enabled before reading XCOMP_BV from init_fpstate.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability listed in the Red Hat kernel security advisory; the provided content does not describe its technical impact.
An unspecified Linux kernel vulnerability included in this Red Hat kernel security advisory; no technical details are provided in the content.
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.