|
Disclosure date: |
 Severity rating: 3.0 Low |
Industry-wide severity ratings can be found in the National Vulnerability Database |
Related Content
Overview
TEE Device Interface Security Protocol (TDISP) and Integrity and Data Encryption (IDE) are industry-standard protocols which were first introduced in the PCI Express (PCIe) Base Specification Revision 6.0. These protocols are used by Intel® Trust Domain Extensions Connect (Intel® TDX Connect) to enforce confidentiality and integrity isolation between TEE Device Interfaces (TDIs) exposed by some PCIe devices while they are being used by Trust Domains (TDs). For example, TDISP defines a protocol that is used by Intel TDX Connect to securely deallocate a TDI from one TD and bind it to a second TD. However, a gap in the current TDISP specification exposes a potential security vulnerability known as Delayed Posted Redirection (DPR), where posted requests (PRs) sent by a TD may be delayed by a malicious programmable PCIe switch until their destination TDI is re-bound to a second TD. Those PRs’ contents may therefore become observable to the second TD (a confidentiality violation) or may overwrite data that belongs to the second TD (an integrity violation). The current TDISP and IDE specifications do not define a policy to securely handle this scenario. Consequently, DPR can affect all compliant platforms, including Intel products.
Intel recommends that programmable PCIe switches should not be used in Intel TDX Connect and IDE deployments that involve an affected processor; see Affected Products.
DPR has been assigned non-Intel issued CVE-2025-9614 with a base score of 3.0 Low CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N.
Mitigation
DPR can be mitigated by refreshing the IDE key(s) used by a TDI, virtual function, or physical function when rebinding the TDI or function to a different TD or VM. When using IDE without Intel TDX Connect1, Intel recommends that the Virtual Machine Monitor (VMM) should refresh IDE key(s) used by a virtual or physical device function before re-assigning the function to a different VM. Intel plans to provide a platform update to further harden Intel TDX Connect by enforcing an IDE key refresh when a TDI is bound to a TD. Intel also recommends that programmable PCIe switches should not be used in Intel TDX Connect and IDE Selective Stream deployments that involve a potentially affected Intel® platform; see Affected Products.
Intel is collaborating with PCI-SIG and industry partners to update the TDISP specification to address this standard-level gap with new implementation guidance for hardware vendors that recommends enforcing an IDE key refresh during TDI reassignment.
Footnotes
- IDE Selective Streams can also be used without Intel TDX Connect to, for example, prevent a malicious switch from attacking PCIe traffic between a virtual machine (VM) and a virtual or physical function exposed by a device. However, DPR may similarly allow a malicious switch to delay PRs sent by the VM until the virtual/physical function has been re-assigned to a different VM.