CVE-2020-29567
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of...
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
6.2
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
- Record
CVE-2020-29567- CVSS 3.1
- 6.2 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - CVSS 2.0
- 4.9 Medium
AV:L/AC:L/Au:N/C:N/I:N/A:C - Weakness
- CWE-770
- Updated
- 2026-11-02
CVE List No score
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
- Record
CVE-2020-29567- Updated
- 2026-11-02
EUVDEUVD-2020-21929 No score
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
- Record
EUVD-2020-21929- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-x993-24wq-x7c4 No score
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of...
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
- Record
GHSA-x993-24wq-x7c4- Weakness
- CWE-770
- Updated
- 2026-11-02
OSVALPINE-CVE-2020-29567
6.2
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
- Record
ALPINE-CVE-2020-29567- CVSS 3.1
- 6.2 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSV
6.2
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
- Record
CVE-2020-29567- CVSS 3.1
- 6.2 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2020-29567
6.2
An issue was discovered in Xen 4.14.x. When moving IRQs between CPUs to distribute the load of IRQ handling, IRQ vectors are dynamically allocated and de-allocated on the relevant CPUs. De-allocation has to happen when certain constraints are met. If these conditions are not met when first checked, the checking CPU may send an interrupt to itself, in the expectation that this IRQ will be delivered only after the condition preventing the cleanup has cleared. For two specific IRQ vectors, this expectation was violated, resulting in a continuous stream of self-interrupts, which renders the CPU effectively unusable. A domain with a passed through PCI device can cause lockup of a physical CPU, resulting in a Denial of Service (DoS) to the entire host. Only x86 systems are vulnerable. Arm systems are not vulnerable. Only guests with physical PCI devices passed through to them can exploit the vulnerability.
- Record
DEBIAN-CVE-2020-29567- CVSS 3.1
- 6.2 Medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVopenSUSE-SU-2024:11520-1 No score
xen-4.15.1_01-1.2 on GA media
These are all security issues fixed in the xen-4.15.1_01-1.2 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:11520-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.13 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.14 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.15 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.16 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.17 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.18 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.19 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.20 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.21 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.22 |
before 4.14.1-r0 | 4.14.1-r0 |
Show 6 moreShow less
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.23 |
before 4.14.1-r0 | 4.14.1-r0 |
xenAlpine:v3.24 |
before 4.14.1-r0 | 4.14.1-r0 |
xenDebian:12 |
before 4.14.0+88-g1d1d1f5391-1 | 4.14.0+88-g1d1d1f5391-1 |
xenDebian:13 |
before 4.14.0+88-g1d1d1f5391-1 | 4.14.0+88-g1d1d1f5391-1 |
xenDebian:14 |
before 4.14.0+88-g1d1d1f5391-1 | 4.14.0+88-g1d1d1f5391-1 |
xenopenSUSE:Tumbleweed From an advisory covering 93 CVEs |
before 4.15.1_01-1.2 | 4.15.1_01-1.2 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2020-29567 is a medium vulnerability (CVSS 6.2) in Xen, published December 15, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.37%, the 30th percentile. Fixed in xen 4.14.1-r0.
References
xenbits.xenproject.org/xsa/advisory-356.html
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OBLV6L6Q24PPQ2CRFXDX4Q76KU776GKI
security.gentoo.org/glsa/202107-30
nvd.nist.gov/vuln/detail/CVE-2020-29567
lists.fedoraproject.org/archives/list/[email protected]/message/OBLV6L6Q24PPQ2CRFXDX4Q76KU776GKI
github.com/advisories/GHSA-x993-24wq-x7c4
Show 95 moreShow less
security.alpinelinux.org/vuln/CVE-2020-29567
security-tracker.debian.org/tracker/CVE-2020-29567
suse.com/security/cve/CVE-2007-1320
suse.com/security/cve/CVE-2007-1366
suse.com/security/cve/CVE-2007-3919
suse.com/security/cve/CVE-2016-10013
suse.com/security/cve/CVE-2016-10024
suse.com/security/cve/CVE-2016-10025
suse.com/security/cve/CVE-2016-7777
suse.com/security/cve/CVE-2016-7908
suse.com/security/cve/CVE-2016-7909
suse.com/security/cve/CVE-2016-8667
suse.com/security/cve/CVE-2016-8669
suse.com/security/cve/CVE-2016-8910
suse.com/security/cve/CVE-2016-9377
suse.com/security/cve/CVE-2016-9379
suse.com/security/cve/CVE-2016-9381
suse.com/security/cve/CVE-2016-9382
suse.com/security/cve/CVE-2016-9383
suse.com/security/cve/CVE-2016-9384
suse.com/security/cve/CVE-2016-9385
suse.com/security/cve/CVE-2016-9386
suse.com/security/cve/CVE-2016-9637
suse.com/security/cve/CVE-2016-9921
suse.com/security/cve/CVE-2016-9932
suse.com/security/cve/CVE-2017-12135
suse.com/security/cve/CVE-2017-12136
suse.com/security/cve/CVE-2017-12137
suse.com/security/cve/CVE-2017-2615
suse.com/security/cve/CVE-2017-2620
suse.com/security/cve/CVE-2017-5753
suse.com/security/cve/CVE-2017-6505
suse.com/security/cve/CVE-2017-8309
suse.com/security/cve/CVE-2017-9330
suse.com/security/cve/CVE-2018-10471
suse.com/security/cve/CVE-2018-10472
suse.com/security/cve/CVE-2018-10981
suse.com/security/cve/CVE-2018-10982
suse.com/security/cve/CVE-2018-12126
suse.com/security/cve/CVE-2018-12891
suse.com/security/cve/CVE-2018-12892
suse.com/security/cve/CVE-2018-12893
suse.com/security/cve/CVE-2018-15468
suse.com/security/cve/CVE-2018-15469
suse.com/security/cve/CVE-2018-15470
suse.com/security/cve/CVE-2018-18883
suse.com/security/cve/CVE-2018-19961
suse.com/security/cve/CVE-2018-19963
suse.com/security/cve/CVE-2018-19964
suse.com/security/cve/CVE-2018-19965
suse.com/security/cve/CVE-2018-19966
suse.com/security/cve/CVE-2018-19967
suse.com/security/cve/CVE-2018-3639
suse.com/security/cve/CVE-2018-3646
suse.com/security/cve/CVE-2018-3665
suse.com/security/cve/CVE-2018-5244
suse.com/security/cve/CVE-2018-7540
suse.com/security/cve/CVE-2018-7541
suse.com/security/cve/CVE-2018-7542
suse.com/security/cve/CVE-2018-8897
suse.com/security/cve/CVE-2019-17349
suse.com/security/cve/CVE-2020-0543
suse.com/security/cve/CVE-2020-11739
suse.com/security/cve/CVE-2020-11740
suse.com/security/cve/CVE-2020-11742
suse.com/security/cve/CVE-2020-11743
suse.com/security/cve/CVE-2020-15563
suse.com/security/cve/CVE-2020-15565
suse.com/security/cve/CVE-2020-15566
suse.com/security/cve/CVE-2020-15567
suse.com/security/cve/CVE-2020-25595
suse.com/security/cve/CVE-2020-25596
suse.com/security/cve/CVE-2020-25597
suse.com/security/cve/CVE-2020-25598
suse.com/security/cve/CVE-2020-25599
suse.com/security/cve/CVE-2020-25600
suse.com/security/cve/CVE-2020-25601
suse.com/security/cve/CVE-2020-25602
suse.com/security/cve/CVE-2020-25603
suse.com/security/cve/CVE-2020-25604
suse.com/security/cve/CVE-2020-27670
suse.com/security/cve/CVE-2020-27671
suse.com/security/cve/CVE-2020-27672
suse.com/security/cve/CVE-2020-27674
suse.com/security/cve/CVE-2020-28368
suse.com/security/cve/CVE-2020-29040
suse.com/security/cve/CVE-2020-29480
suse.com/security/cve/CVE-2020-29481
suse.com/security/cve/CVE-2020-29483
suse.com/security/cve/CVE-2020-29484
suse.com/security/cve/CVE-2020-29566
suse.com/security/cve/CVE-2020-29567
suse.com/security/cve/CVE-2020-29570
suse.com/security/cve/CVE-2020-29571
suse.com/security/cve/CVE-2021-28687