Loading vulnerability…
CVE-2024-47727 is an improper validation vulnerability in the Linux kernel x86 Trusted Domain Extensions (TDX) MMIO exception-handling path. The handle_mmio() function checked whether a virtualization exception (#VE) occurred while executing in kernel mode, but did not verify that the MMIO target address was in kernel address space before decoding the instruction. A userspace process could provide an MMIO address to a system call that performs get_user() or put_user(), causing an MMIO #VE that the kernel misclassified as a kernel-initiated MMIO operation.
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.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Incorrect in-kernel MMIO validation in Linux kernel x86 TDX.
Linux kernel vulnerability addressed by the referenced AlmaLinux/TuxCare update.
A Linux kernel x86 Trusted Domain Extensions (TDX) flaw involving the in-kernel MMIO check.
Linux kernel x86 Trusted Domain Extensions (TDX) flaw involving the in-kernel MMIO check.
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.