Loading vulnerability…
CVE-2024-25742, also known as WeSee, affects Linux kernels before 6.9 running as AMD SEV-ES or SEV-SNP confidential-computing guests. An untrusted hypervisor can inject virtual interrupt vector 29, causing a forged VMM Communication Exception (#VC), at arbitrary points during guest execution. The guest #VC handler fails to validate that the interrupted instruction legitimately generated a #VC before processing the exception and exchanging emulation state with the hypervisor. Forged exceptions can therefore cause attacker-controlled values to be consumed by the guest handler or sensitive guest state to be returned to the hypervisor.
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.
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
WeSee is a vulnerability in AMD SEV-SNP's handling of injected VMM Communication Exceptions (#VC). A malicious cloud hypervisor can inject crafted #VC exceptions at chosen execution points, causing the guest's #VC handler to emulate attacker-selected operations and violate SEV-SNP confidentiality and integrity guarantees. Demonstrated impacts include leaking NGINX kernel-TLS session keys, altering firewall rules, and injecting kernel-space code to obtain a root shell.
AMD hardware/kernel issue involving an instruction raising a #VC exception at exit.
Linux kernel AMD hardware virtualization flaw involving a #VC exception at guest exit.
A Linux kernel AMD hardware/virtualization vulnerability addressed by correcting handling of an instruction that raises a #VC exception at exit.
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.