CVE-2024-50102 is an x86 speculative-execution information-disclosure vulnerability in Linux kernel user-address validation and masking. AMD Zen 5 processors rename the AC bit, so STAC/CLAC no longer provide the execution-serialization behavior on which affected kernel paths relied. A non-canonical kernel-space address can consequently transiently bypass sign-bit-based user-address classification and yield speculative data that a suitable disclosure gadget can encode. Affected paths include user-address masking, valid_user_address() as used by access_ok(), and assembly sign-bit checks in get_user() helpers. put_user() and clear_user() variants are not affected because they do not yield a speculative result usable by a gadget.
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 user-address-masking flaw involving speculation on non-canonical addresses.
Non-canonical-address speculative-execution issue in Linux kernel x86 user address masking.
A Linux kernel x86 speculative-execution information-disclosure vulnerability affecting handling of non-canonical user addresses, particularly on AMD Zen 5 where STAC/CLAC no longer serializes execution and a speculative data-leak window can remain open.
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.