CVE-2025-1713 | deadlock potential with VT-d and legacy PCI device pass-through

When setting up interrupt remapping for legacy PCI(-X) devices, including PCI(-X) bridges, a lookup of the upstream bridge is required. This lookup, itself involving acquiring of a lock, is done in a context where acquiring that lock is unsafe. This can lead to a deadlock.

Published: 2025-07-17 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-1713 is rated Moderate Risk (47.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.69%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-1713

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.23% 0.69% +0.46%
2 2026-05-13 0.09% 0.23% +0.15%
3 2026-04-07 — 0.09% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-1713

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-1713

OS Trackers for CVE-2025-1713

vendor priority summary link
alpine — CVE-2025-1713: 1 source package rows (xen); 428 state rows across 7 repos (3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 56, open 372. https://security.alpinelinux.org/vuln/CVE-2025-1713
debian end-of-life CVE-2025-1713 end-of-life priority: Debian including 1 source packages (xen), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-1713
suse medium — https://www.suse.com/security/cve/CVE-2025-1713/
ubuntu medium CVE-2025-1713 medium priority: Ubuntu including 1 source packages (xen), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 2. https://ubuntu.com/security/CVE-2025-1713

Affected software / configurations for CVE-2025-1713

Vendor Product Version Raw CPE
xen xen >= 4.0.0 cpe:2.3:o:xen:xen:*:*:*:*:*:*:x86:*

References for CVE-2025-1713

cvelogic Threat Intelligence