CVE-2025-9613 is a vulnerability in the PCI Express (PCIe) Integrity and Data Encryption (IDE) specification, affecting PCIe Base Specification Revision 5.0 and later. The flaw arises from insufficient guidance on tag reuse after completion timeouts, which may allow multiple outstanding Non-Posted Requests to share the same tag. This tag aliasing condition can result in completions being delivered to the wrong security context, potentially compromising data integrity and confidentiality. The vulnerability is specification-level and impacts hardware and firmware implementations of PCIe IDE, particularly in environments where data integrity is critical.
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 flaw in PCIe 6.0's IDE mechanism where improper timeout flushing allows attackers with local access to inject packets with matching tags, causing the receiver to accept incorrect data.
A vulnerability in the PCIe IDE protocol where incomplete flushing of a completion timeout may allow a receiver to accept incorrect data if an attacker injects a packet with a matching tag.
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.