Описание
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.
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2025-1713
- https://xenbits.xenproject.org/xsa/advisory-467.html
- http://www.openwall.com/lists/oss-security/2025/02/27/1
- http://www.openwall.com/lists/oss-security/2025/02/27/3
- http://www.openwall.com/lists/oss-security/2025/02/28/1
- http://xenbits.xen.org/xsa/advisory-467.html
Связанные уязвимости
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.
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.
When setting up interrupt remapping for legacy PCI(-X) devices, includ ...
