CVE-2024-39483 is a flaw in the Linux kernel KVM implementation for AMD Secure Virtual Machine (SVM) virtual-NMI handling. KVM could issue a WARN when an NMI window was requested while virtual-NMI support was enabled, even when NMIs were not masked. This can occur when KVM cannot immediately inject an NMI because the virtual CPU is in an STI interrupt shadow or is executing with GIF cleared. The corrected logic emits the warning only when NMIs are actually masked because the virtual CPU is already handling an NMI.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel KVM/SVM vulnerability concerning vNMI and NMI-window handling when NMIs are masked.
A Linux kernel KVM SVM issue involving warning behavior for virtual NMI and NMI-window conditions when NMIs are masked.
Linux kernel KVM/SVM issue involving virtual NMI and NMI-window handling when NMIs are masked.
A Linux kernel KVM/SVM issue involving handling of virtual NMIs and NMI-window conditions.
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.