Loading vulnerability…
CVE-2025-30513 is a race condition vulnerability affecting certain Intel Trust Domain Extensions (TDX) Module components operating within Ring 0. The flaw allows a hypervisor-controlled execution context to trigger an escalation of privilege under specific timing conditions. Intel describes the issue as exploitable by a system software adversary with privileged local access, using a low-complexity attack that does not require user interaction. The vulnerability is associated with the TDX 1.5 security review and affects a highly privileged component in the trusted computing base, creating a path for unauthorized privilege gain through improper handling of concurrent operations in the module.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A third-party component vulnerability addressed by ASUS BIOS version 3003 / Secure Boot DBX Update 06102025 for affected ASUS GPU servers.
One of five reported vulnerabilities affecting Intel Trust Domain Extensions (TDX) 1.5; specific impact details are not provided in the content.
A locally exploitable vulnerability in Intel processors (Intel TDX module per INTEL-SA-01397) impacting certain HPE StoreEasy servers, with potential for privilege escalation and/or information disclosure/DoS.
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.