CVE-2025-1713
published 2025-07-17CVE-2025-1713: 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…
PriorityP338high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
0.72%
50.2th percentile
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.
Affected
11 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | xen | < xen 4.17.5+72-g01140da4e8-1 (bookworm) | xen 4.17.5+72-g01140da4e8-1 (bookworm) |
| xen | xen | >= 0 < 4.17.5-r3 | 4.17.5-r3 |
| xen | xen | >= 0 < 4.18.4-r1 | 4.18.4-r1 |
| xen | xen | >= 0 < 4.18.4-r1 | 4.18.4-r1 |
| xen | xen | >= 0 < 4.19.2-r0 | 4.19.2-r0 |
| xen | xen | >= 0 < 4.19.1-r1 | 4.19.1-r1 |
| xen | xen | >= 0 < 4.19.1-r1 | 4.19.1-r1 |
| xen | xen | >= 0 < 4.17.5+72-g01140da4e8-1 | 4.17.5+72-g01140da4e8-1 |
| xen | xen | >= 0 < 4.20.0-1 | 4.20.0-1 |
| xen | xen | >= 0 < 4.20.0-1 | 4.20.0-1 |
| xen | xen | >= 4.0.0 | — |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2025-1713: xen - When setting up interrupt remapping for legacy PCI(-X) devices, including PCI(-X...
vendor_debian·2025·CVSS 7.5
CVE-2025-1713 [HIGH] CVE-2025-1713: xen - When setting up interrupt remapping for legacy PCI(-X) devices, including PCI(-X...
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.
Scope: local
bookworm: resolved (fixed in 4.17.5+72-g01140da4e8-1)
bullseye: open
forky: resolved (fixed in 4.20.0-1)
sid: resolved (fixed in 4.20.0-1)
trixie: resolved (fixed in 4.20.0-1)
OSV
CVE-2025-1713: When setting up interrupt remapping for legacy PCI(-X) devices, including PCI(-X) bridges, a lookup of the upstream bridge is required
osv·2025-07-17·CVSS 7.5
CVE-2025-1713 [HIGH] CVE-2025-1713: When setting up interrupt remapping for legacy PCI(-X) devices, including PCI(-X) bridges, a lookup of the upstream bridge is required
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.
GHSA
GHSA-h63j-vf47-m3ch: When setting up interrupt remapping for legacy PCI(-X) devices,
including PCI(-X) bridges, a lookup of the upstream bridge is required
ghsa_unreviewed·2025-07-17
CVE-2025-1713 [HIGH] CWE-833 GHSA-h63j-vf47-m3ch: When setting up interrupt remapping for legacy PCI(-X) devices,
including PCI(-X) bridges, a lookup of the upstream bridge is required
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.
OSV
CVE-2025-1713: When setting up interrupt remapping for legacy PCI(-X) devices,
including PCI(-X) bridges, a lookup of the upstream bridge is required
osv·2025-07-17·CVSS 7.5
CVE-2025-1713 [HIGH] CVE-2025-1713: When setting up interrupt remapping for legacy PCI(-X) devices,
including PCI(-X) bridges, a lookup of the upstream bridge is required
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-07-17
Published