# CVE-2025-9613: CVE-2025-9613

> Insufficient tag reuse guidance in PCIe IDE allows tag aliasing, potentially delivering completions to wrong security contexts and compromising data integrity.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 10 Dec 2025
- **Also known as:** GHSA-p754-4xmg-g83j

## What is CVE-2025-9613?

CVE-2025-9613 is a medium-severity vulnerability in PCI-SIG PCI Express Integrity and Data Encryption (PCIe IDE) Specification, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was discovered in the PCI Express (PCIe) Integrity and Data Encryption (IDE) specification, where insufficient guidance on tag reuse after completion timeouts 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.

## Which versions are affected by CVE-2025-9613?

It affects 1 product.


Products: Pcisig Pci Express Integrity and Data Encryption.

## How do I fix CVE-2025-9613?

No fix has been published for CVE-2025-9613 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9613 being exploited?

There is no known exploitation of CVE-2025-9613 in the wild and no public exploit code.

## Other vulnerabilities in PCI-SIG PCI Express Integrity and Data Encryption (PCIe IDE) Specification

- [CVE-2025-9614](https://insights.sbomify.com/CVE-2025-9614/): CVE-2025-9614 (medium 6.5)
- [CVE-2025-9612](https://insights.sbomify.com/CVE-2025-9612/): CVE-2025-9612 (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9613 and fix it if it is affected.

What it is: CVE-2025-9613 is a medium-severity vulnerability in PCI-SIG PCI Express Integrity and Data Encryption (PCIe IDE) Specification, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9613 in the wild and no public exploit code.

Affected product: PCI-SIG PCI Express Integrity and Data Encryption (PCIe IDE) Specification. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9613/ (Markdown: https://insights.sbomify.com/CVE-2025-9613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9613
- OSV: https://osv.dev/vulnerability/CVE-2025-9613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9613/
Summaries are generated and may contain mistakes; the official description above is the record.