Loading vulnerability…
CVE-2025-9612 is a specification-level vulnerability in the PCI Express (PCIe) Integrity and Data Encryption (IDE) protocol, affecting PCIe Base Specification Revision 5.0 and later. The flaw arises from insufficient guidance on Transaction Layer Packet (TLP) ordering and tag uniqueness, resulting in a missing integrity check that allows encrypted packets to be replayed or reordered without detection. This enables a local or physical attacker with access to the PCIe bus to inject stale or corrupted data into secure PCIe data streams, violating the intended data integrity protections of the IDE mechanism. The vulnerability impacts systems using PCIe IDE, including major server processors from Intel and AMD, and could undermine trusted execution environments.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specification-level flaw in PCIe 6.0's IDE mechanism where a missing integrity check allows attackers with local access to reorder PCIe traffic, causing the receiver to process stale data and potentially compromising data integrity.
A vulnerability in the PCIe IDE protocol where a missing integrity check on a receiving port may allow re-ordering of PCIe traffic, leading to the processing of stale data.
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.