CVE-2020-15567
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges...
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
CVE-2020-15567- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - CVSS 2.0
- 4.4 Medium
AV:L/AC:M/Au:N/C:P/I:P/A:P - Weakness
- CWE-362
- Updated
- 2026-11-02
CVE List No score
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
CVE-2020-15567- Updated
- 2026-11-02
EUVDEUVD-2020-7554 No score
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
EUVD-2020-7554- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-mpwm-7x8j-q5j2
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges...
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
GHSA-mpwm-7x8j-q5j2- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-362
- Updated
- 2026-11-02
OSVALPINE-CVE-2020-15567
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
ALPINE-CVE-2020-15567- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSV
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
CVE-2020-15567- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
Show 14 moreShow less
OSVDEBIAN-CVE-2020-15567
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
DEBIAN-CVE-2020-15567- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2020-15567
An issue was discovered in Xen through 4.13.x, allowing Intel guest OS users to gain privileges or cause a denial of service because of non-atomic modification of a live EPT PTE. When mapping guest EPT (nested paging) tables, Xen would in some circumstances use a series of non-atomic bitfield writes. Depending on the compiler version and optimisation flags, Xen might expose a dangerous partially written PTE to the hardware, which an attacker might be able to race to exploit. A guest administrator or perhaps even an unprivileged guest user might be able to cause denial of service, data corruption, or privilege escalation. Only systems using Intel CPUs are vulnerable. Systems using AMD CPUs, and Arm systems, are not vulnerable. Only systems using nested paging (hap, aka nested paging, aka in this case Intel EPT) are vulnerable. Only HVM and PVH guests can exploit the vulnerability. The presence and scope of the vulnerability depends on the precise optimisations performed by the compiler used to build Xen. If the compiler generates (a) a single 64-bit write, or (b) a series of read-modify-write operations in the same order as the source code, the hypervisor is not vulnerable. For example, in one test build using GCC 8.3 with normal settings, the compiler generated multiple (unlocked) read-modify-write operations in source-code order, which did not constitute a vulnerability. We have not been able to survey compilers; consequently we cannot say which compiler(s) might produce vulnerable code (with which code-generation options). The source code clearly violates the C rules, and thus should be considered vulnerable.
- Record
UBUNTU-CVE-2020-15567- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVopenSUSE-SU-2020:0965-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15566: Fixed incorrect error handling in event channel port allocation (bsc#1173376).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- CVE-2020-0543: Special Register Buffer Data Sampling (SRBDS) aka 'CrossTalk' (bsc#1172205).
Additional upstream bug fixes (bsc#1027519)
This update was imported from the SUSE:SLE-15-SP1:Update update project.
- Record
openSUSE-SU-2020:0965-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2020:0985-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15566: Fixed incorrect error handling in event channel port allocation (bsc#1173376).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- CVE-2020-0543: Special Register Buffer Data Sampling (SRBDS) aka 'CrossTalk' (bsc#1172205).
Additional upstream bug fixes (bsc#1027519)
This update was imported from the SUSE:SLE-15-SP2:Update update project.
- Record
openSUSE-SU-2020:0985-1- 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
OSVSUSE-SU-2020:14521-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-0543: Fixed a leak of Special Register Buffer Data Sampling (SRBDS) aka 'CrossTalk' (bsc#1172205,XSA-320)
- CVE-2020-14364: Fixed an out-of-bounds read/write access while processing usb packets (bsc#1175534).
- CVE-2020-15565: Fixed an issue cache write (bsc#1173378,XSA-321).
- CVE-2020-15567: Fixed an issue with non-atomic modification of live EPT PTE (bsc#1173380,XSA-328)
- CVE-2020-25595: Fixed an issue where PCI passthrough code was reading back hardware registers (bsc#1176344,XSA-337)
- CVE-2020-25596: Fixed a potential denial of service in x86 pv guest kernel via SYSENTER (bsc#1176345,XSA-339)
- CVE-2020-25597: Fixed an issue where a valid event channels may not turn invalid (bsc#1176346,XSA-338)
- CVE-2020-25600: Fixed out of bounds event channels available to 32-bit x86 domains (bsc#1176348,XSA-342)
- CVE-2020-25601: Fixed an issue due to lack of preemption in evtchn_reset() / evtchn_destroy() (bsc#1176350,XSA-344)
- CVE-2020-25603: Fixed an issue due to missing barriers when accessing/allocating an event channel (bsc#1176347,XSA-340)
- CVE-2020-25604: Fixed a race condition when migrating timers between x86 HVM vCPU-s (bsc#1176343,XSA-336)
- Record
SUSE-SU-2020:14521-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:1886-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- Record
SUSE-SU-2020:1886-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:1887-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15566: Fixed incorrect error handling in event channel port allocation (bsc#1173376).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- CVE-2020-0543: Special Register Buffer Data Sampling (SRBDS) aka 'CrossTalk' (bsc#1172205).
Additional upstream bug fixes (bsc#1027519)
- Record
SUSE-SU-2020:1887-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:1888-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15566: Fixed incorrect error handling in event channel port allocation (bsc#1173376).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- Record
SUSE-SU-2020:1888-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:1889-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15566: Fixed incorrect error handling in event channel port allocation (bsc#1173376).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- CVE-2020-0543: Special Register Buffer Data Sampling (SRBDS) aka 'CrossTalk' (bsc#1172205).
Additional upstream bug fixes (bsc#1027519)
- Record
SUSE-SU-2020:1889-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:1891-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15566: Fixed incorrect error handling in event channel port allocation (bsc#1173376).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- Record
SUSE-SU-2020:1891-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:1902-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-15563: Fixed inverted code paths in x86 dirty VRAM tracking (bsc#1173377).
- CVE-2020-15565: Fixed insufficient cache write-back under VT-d (bsc#1173378).
- CVE-2020-15566: Fixed incorrect error handling in event channel port allocation (bsc#1173376).
- CVE-2020-15567: Fixed non-atomic modification of live EPT PTE (bsc#1173380).
- CVE-2020-0543: Special Register Buffer Data Sampling (SRBDS) aka 'CrossTalk' (bsc#1172205).
Additional upstream bug fixes (bsc#1027519)
- Record
SUSE-SU-2020:1902-1- Updated
- 2026-11-02
OSVSUSE-SU-2020:2822-1 No score
Security update for xen
This update for xen fixes the following issues:
- CVE-2020-25604: Fixed a race condition when migrating timers between x86 HVM vCPU-s (bsc#1176343,XSA-336)
- CVE-2020-25595: Fixed an issue where PCI passthrough code was reading back hardware registers (bsc#1176344,XSA-337)
- CVE-2020-25597: Fixed an issue where a valid event channels may not turn invalid (bsc#1176346,XSA-338)
- CVE-2020-25596: Fixed a potential denial of service in x86 pv guest kernel via SYSENTER (bsc#1176345,XSA-339)
- CVE-2020-25603: Fixed an issue due to missing barriers when accessing/allocating an event channel (bsc#1176347,XSA-340)
- CVE-2020-25600: Fixed out of bounds event channels available to 32-bit x86 domains (bsc#1176348,XSA-342)
- CVE-2020-25599: Fixed race conditions with evtchn_reset() (bsc#1176349,XSA-343)
- CVE-2020-25601: Fixed an issue due to lack of preemption in evtchn_reset() / evtchn_destroy() (bsc#1176350,XSA-344)
- CVE-2020-14364: Fixed an out-of-bounds read/write access while processing usb packets (bsc#1175534).
- CVE-2020-0543: Fixed a leak of Special Register Buffer Data Sampling (SRBDS) aka 'CrossTalk' (bsc#1172205,XSA-320)
- CVE-2020-15565: Fixed an issue cache write (bsc#1173378,XSA-321).
- CVE-2020-15567: Fixed an issue with non-atomic modification of live EPT PTE (bsc#1173380,XSA-328)
- Record
SUSE-SU-2020:2822-1- Updated
- 2026-11-02
OSVUSN-5617-1 No score
xen vulnerabilities
It was discovered that memory contents previously stored in microarchitectural special registers after RDRAND, RDSEED, and SGX EGETKEY read operations on Intel client and Xeon E3 processors may be briefly exposed to processes on the same or different processor cores. A local attacker could use this to expose sensitive information. (CVE-2020-0543)
Julien Grall discovered that Xen incorrectly handled memory barriers on ARM-based systems. An attacker could possibly use this issue to cause a denial of service, obtain sensitive information or escalate privileges. (CVE-2020-11739)
Ilja Van Sprundel discovered that Xen incorrectly handled profiling of guests. An unprivileged attacker could use this issue to obtain sensitive information from other guests, cause a denial of service or possibly gain privileges. (CVE-2020-11740, CVE-2020-11741)
It was discovered that Xen incorrectly handled grant tables. A malicious guest could possibly use this issue to cause a denial of service. (CVE-2020-11742, CVE-2020-11743)
Jan Beulich discovered that Xen incorrectly handled certain code paths. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-15563)
Julien Grall discovered that Xen incorrectly verified memory addresses provided by the guest on ARM-based systems. A malicious guest administrator could possibly use this issue to cause a denial of service. (CVE-2020-15564)
Roger Pau Monné discovered that Xen incorrectly handled caching on x86 Intel systems. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-15565)
It was discovered that Xen incorrectly handled error in event-channel port allocation. A malicious guest could possibly use this issue to cause a denial of service. (CVE-2020-15566)
Jan Beulich discovered that Xen incorrectly handled certain EPT (Extended Page Tables). An attacker could possibly use this issue to cause a denial of service, data corruption or privilege escalation. (CVE-2020-15567)
Andrew Cooper discovered that Xen incorrectly handled PCI passthrough. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-25595)
Andrew Cooper discovered that Xen incorrectly sanitized path injections. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-25596)
Jan Beulich discovered that Xen incorrectly handled validation of event channels. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-25597)
Julien Grall and Jan Beulich discovered that Xen incorrectly handled resetting event channels. An attacker could possibly use this issue to cause a denial of service or obtain sensitive information. (CVE-2020-25599)
Julien Grall discovered that Xen incorrectly handled event channels memory allocation on 32-bits domains. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-25600)
Jan Beulich discovered that Xen incorrectly handled resetting or cleaning up event channels. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-25601)
Andrew Cooper discovered that Xen incorrectly handled certain Intel specific MSR (Model Specific Registers). An attacker could possibly use this issue to cause a denial of service. (CVE-2020-25602)
Julien Grall discovered that Xen incorrectly handled accessing/allocating event channels. An attacker could possibly use this issue to cause a denial of service, obtain sensitive information of privilege escalation. (CVE-2020-25603)
Igor Druzhinin discovered that Xen incorrectly handled locks. An attacker could possibly use this issue to cause a denial of service. (CVE-2020-25604)
- Record
USN-5617-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.10 |
before 4.12.3-r2 | 4.12.3-r2 |
xenAlpine:v3.11 |
before 4.13.1-r2 | 4.13.1-r2 |
xenAlpine:v3.12 |
before 4.13.1-r2 | 4.13.1-r2 |
xenAlpine:v3.13 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.14 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.15 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.16 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.17 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.18 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.19 |
before 4.13.1-r4 | 4.13.1-r4 |
Show 43 moreShow less
| Package | Affected | Fixed |
|---|---|---|
xenAlpine:v3.20 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.21 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.22 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.23 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.24 |
before 4.13.1-r4 | 4.13.1-r4 |
xenAlpine:v3.9 |
before 4.11.4-r0 | 4.11.4-r0 |
xenDebian:12 |
before 4.11.4+24-gddaaccbbab-1 | 4.11.4+24-gddaaccbbab-1 |
xenDebian:13 |
before 4.11.4+24-gddaaccbbab-1 | 4.11.4+24-gddaaccbbab-1 |
xenDebian:14 |
before 4.11.4+24-gddaaccbbab-1 | 4.11.4+24-gddaaccbbab-1 |
xenDebian:10 From an advisory covering 10 CVEs |
before 4.11.4+24-gddaaccbbab-1~deb10u1, plus listed versions 4.11.1+92-g6c33308a8d-24.11.3+24-g14b62ab3e5-14.11.3+24-g14b62ab3e5-1~deb10u14.11.4-1 |
4.11.4+24-gddaaccbbab-1~deb10u1 |
xenSUSE:Linux Enterprise Server 11 SP4-LTSS From an advisory covering 11 CVEs |
before 4.4.4_44-61.55.1 | 4.4.4_44-61.55.1 |
xenSUSE:HPE Helion OpenStack 8 From an advisory covering 3 CVEs |
before 4.9.4_08-3.66.1 | 4.9.4_08-3.66.1 |
xenSUSE:OpenStack Cloud 8 From an advisory covering 3 CVEs |
before 4.9.4_08-3.66.1 | 4.9.4_08-3.66.1 |
xenSUSE:OpenStack Cloud Crowbar 8 From an advisory covering 3 CVEs |
before 4.9.4_08-3.66.1 | 4.9.4_08-3.66.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP3 From an advisory covering 3 CVEs |
before 4.9.4_08-3.66.1 | 4.9.4_08-3.66.1 |
xenSUSE:Linux Enterprise Server 12 SP3-LTSS From an advisory covering 3 CVEs |
before 4.9.4_08-3.66.1 | 4.9.4_08-3.66.1 |
xenSUSE:Linux Enterprise Server 12 SP3-BCL From an advisory covering 3 CVEs |
before 4.9.4_08-3.66.1 | 4.9.4_08-3.66.1 |
xenSUSE:Enterprise Storage 5 From an advisory covering 3 CVEs |
before 4.9.4_08-3.66.1 | 4.9.4_08-3.66.1 |
xenSUSE:Linux Enterprise Software Development Kit 12 SP5 From an advisory covering 5 CVEs |
before 4.12.3_04-3.18.1 | 4.12.3_04-3.18.1 |
xenSUSE:Linux Enterprise Server 12 SP5 From an advisory covering 5 CVEs |
before 4.12.3_04-3.18.1 | 4.12.3_04-3.18.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP5 From an advisory covering 5 CVEs |
before 4.12.3_04-3.18.1 | 4.12.3_04-3.18.1 |
xenSUSE:Linux Enterprise High Performance Computing 15-ESPOS From an advisory covering 4 CVEs |
before 4.10.4_12-3.35.1 | 4.10.4_12-3.35.1 |
xenSUSE:Linux Enterprise High Performance Computing 15-LTSS From an advisory covering 4 CVEs |
before 4.10.4_12-3.35.1 | 4.10.4_12-3.35.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 15 From an advisory covering 4 CVEs |
before 4.10.4_12-3.35.1 | 4.10.4_12-3.35.1 |
xenSUSE:Linux Enterprise Module for Basesystem 15 SP1 From an advisory covering 5 CVEs |
before 4.12.3_04-3.22.1 | 4.12.3_04-3.22.1 |
xenSUSE:Linux Enterprise Module for Server Applications 15 SP1 From an advisory covering 5 CVEs |
before 4.12.3_04-3.22.1 | 4.12.3_04-3.22.1 |
xenSUSE:OpenStack Cloud 9 From an advisory covering 4 CVEs |
before 4.11.4_04-2.30.1 | 4.11.4_04-2.30.1 |
xenSUSE:OpenStack Cloud Crowbar 9 From an advisory covering 4 CVEs |
before 4.11.4_04-2.30.1 | 4.11.4_04-2.30.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP4 From an advisory covering 4 CVEs |
before 4.11.4_04-2.30.1 | 4.11.4_04-2.30.1 |
xenSUSE:Linux Enterprise Server 12 SP4-LTSS From an advisory covering 4 CVEs |
before 4.11.4_04-2.30.1 | 4.11.4_04-2.30.1 |
xenSUSE:Linux Enterprise Module for Basesystem 15 SP2 From an advisory covering 5 CVEs |
before 4.13.1_04-3.4.1 | 4.13.1_04-3.4.1 |
xenSUSE:Linux Enterprise Module for Server Applications 15 SP2 From an advisory covering 5 CVEs |
before 4.13.1_04-3.4.1 | 4.13.1_04-3.4.1 |
xenSUSE:OpenStack Cloud 7 From an advisory covering 12 CVEs |
before 4.7.6_10-43.67.1 | 4.7.6_10-43.67.1 |
xenSUSE:Linux Enterprise Server for SAP Applications 12 SP2 From an advisory covering 12 CVEs |
before 4.7.6_10-43.67.1 | 4.7.6_10-43.67.1 |
xenSUSE:Linux Enterprise Server 12 SP2-LTSS From an advisory covering 12 CVEs |
before 4.7.6_10-43.67.1 | 4.7.6_10-43.67.1 |
xenSUSE:Linux Enterprise Server 12 SP2-BCL From an advisory covering 12 CVEs |
before 4.7.6_10-43.67.1 | 4.7.6_10-43.67.1 |
xenUbuntu:16.04:LTS |
All versions, plus listed versions 4.5.1-0ubuntu14.5.1-0ubuntu24.6.0-1ubuntu14.6.0-1ubuntu24.6.0-1ubuntu4 Show 7 moreShow less4.6.0-1ubuntu4.14.6.0-1ubuntu4.24.6.0-1ubuntu4.34.6.5-0ubuntu14.6.5-0ubuntu1.14.6.5-0ubuntu1.24.6.5-0ubuntu1.4 |
None known |
xenUbuntu:18.04:LTS |
All versions, plus listed versions 4.9.0-0ubuntu34.9.0-0ubuntu44.9.2-0ubuntu1 |
None known |
xenUbuntu:20.04:LTS |
before 4.11.3+24-g14b62ab3e5-1ubuntu2.3, plus listed versions 4.9.2-0ubuntu24.9.2-0ubuntu64.9.2-0ubuntu74.11.3+24-g14b62ab3e5-1ubuntu14.11.3+24-g14b62ab3e5-1ubuntu24.11.3+24-g14b62ab3e5-1ubuntu2.2 |
4.11.3+24-g14b62ab3e5-1ubuntu2.3 |
xenUbuntu:20.04:LTS From an advisory covering 20 CVEs |
before 4.11.3+24-g14b62ab3e5-1ubuntu2.3, plus listed versions 4.9.2-0ubuntu24.9.2-0ubuntu64.9.2-0ubuntu74.11.3+24-g14b62ab3e5-1ubuntu14.11.3+24-g14b62ab3e5-1ubuntu24.11.3+24-g14b62ab3e5-1ubuntu2.2 |
4.11.3+24-g14b62ab3e5-1ubuntu2.3 |
xenopenSUSE:Leap 15.1 From an advisory covering 5 CVEs |
before 4.12.3_04-lp151.2.21.1 | 4.12.3_04-lp151.2.21.1 |
xenopenSUSE:Leap 15.2 From an advisory covering 5 CVEs |
before 4.13.1_04-lp152.2.3.1 | 4.13.1_04-lp152.2.3.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-15567 is a high vulnerability (CVSS 7.8) in Xen, published July 7, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.28%, the 20th percentile. Fixed in xen 4.12.3-r2.
References
xenbits.xen.org/xsa/advisory-328.html
openwall.com/lists/oss-security/2020/07/07/6
debian.org/security/2020/dsa-4723
lists.opensuse.org/opensuse-security-announce/2020-07/msg00024.html
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VB3QJJZV23Z2IDYEMIHELWYSQBUEW6JP
Show 149 moreShow less
security.gentoo.org/glsa/202007-02
nvd.nist.gov/vuln/detail/CVE-2020-15567
github.com/advisories/GHSA-mpwm-7x8j-q5j2
security.alpinelinux.org/vuln/CVE-2020-15567
security-tracker.debian.org/tracker/CVE-2020-15567
suse.com/support/update/announcement/2020/suse-su-202014521-1
bugzilla.suse.com/1172205
ubuntu.com/security/CVE-2020-15567
cve.org/CVERecord?id=CVE-2020-15567