Every CVE Search/ Get API key

CVE-2020-11739

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of...

7.8 HighFix available

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

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

0.29%Down 2.3 points since Apr 14, 2021
90%50%10%1%

What each source reports

NVD Score used 7.8

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
CVE-2020-11739
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS 2.0
6.9 MediumAV:L/AC:M/Au:N/C:C/I:C/A:C
Weakness
CWE-362
Updated
2026-11-02
CVE List No score

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
CVE-2020-11739
Updated
2026-11-02
EUVDEUVD-2020-4081 No score

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
EUVD-2020-4081
Updated
2026-11-03
GitHub AdvisoriesGHSA-5wwp-3576-jfjc 7.8

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of...

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
GHSA-5wwp-3576-jfjc
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Weakness
CWE-119, CWE-362
Updated
2026-11-02
OSVALPINE-CVE-2020-11739 7.8

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
ALPINE-CVE-2020-11739
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Updated
2026-11-02
OSV 7.8

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
CVE-2020-11739
CVSS 3.1
7.8 HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Updated
2026-11-02
Show 11 moreShow less
OSVDEBIAN-CVE-2020-11739 7.8

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
DEBIAN-CVE-2020-11739
CVSS 3.1
7.8 HighCVSS: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-11739 7.8

An issue was discovered in Xen through 4.13.x, allowing guest OS users to cause a denial of service or possibly gain privileges because of missing memory barriers in read-write unlock paths. The read-write unlock paths don't contain a memory barrier. On Arm, this means a processor is allowed to re-order the memory access with the preceding ones. In other words, the unlock may be seen by another processor before all the memory accesses within the "critical" section. As a consequence, it may be possible to have a writer executing a critical section at the same time as readers or another writer. In other words, many of the assumptions (e.g., a variable cannot be modified after a check) in the critical sections are not safe anymore. The read-write locks are used in hypercalls (such as grant-table ones), so a malicious guest could exploit the race. For instance, there is a small window where Xen can leak memory if XENMAPSPACE_grant_table is used concurrently. A malicious guest may be able to leak memory, or cause a hypervisor crash resulting in a Denial of Service (DoS). Information leak and privilege escalation cannot be excluded.

Record
UBUNTU-CVE-2020-11739
CVSS 3.1
7.8 HighCVSS: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:0599-1 No score

Security update for xen

This update for xen fixes the following issues:

Security issues fixed:

  • CVE-2020-11742: Bad continuation handling in GNTTABOP_copy (bsc#1169392).
  • CVE-2020-11740, CVE-2020-11741: xen: XSA-313 multiple xenoprof issues (bsc#1168140).
  • CVE-2020-11739: Missing memory barriers in read-write unlock paths (bsc#1168142).
  • CVE-2020-11743: Bad error path in GNTTABOP_map_grant (bsc#1168143).
  • arm: a CPU may speculate past the ERET instruction (bsc#1160932).

Non-security issues fixed:

  • Xenstored Crashed during VM install (bsc#1167152)
  • DomU hang: soft lockup CPU #0 stuck under high load (bsc#1165206, bsc#1134506)
  • Update API compatibility versions, fixes issues for libvirt. (bsc#1167007, bsc#1157490)
  • aacraid blocks xen commands (bsc#1155200)

This update was imported from the SUSE:SLE-15-SP1:Update update project.

Record
openSUSE-SU-2020:0599-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:1124-1 No score

Security update for xen

This update for xen fixes the following issues:

Security issues fixed:

  • CVE-2020-11742: Bad continuation handling in GNTTABOP_copy (bsc#1169392).
  • CVE-2020-11740, CVE-2020-11741: xen: XSA-313 multiple xenoprof issues (bsc#1168140).
  • CVE-2020-11739: Missing memory barriers in read-write unlock paths (bsc#1168142).
  • CVE-2020-11743: Bad error path in GNTTABOP_map_grant (bsc#1168143).
  • arm: a CPU may speculate past the ERET instruction (bsc#1160932).

Non-security issues fixed:

  • Xenstored Crashed during VM install (bsc#1167152)
  • DomU hang: soft lockup CPU #0 stuck under high load (bsc#1165206, bsc#1134506)
  • Update API compatibility versions, fixes issues for libvirt. (bsc#1167007, bsc#1157490)
  • aacraid blocks xen commands (bsc#1155200)
Record
SUSE-SU-2020:1124-1
Updated
2026-11-02
OSVSUSE-SU-2020:1138-1 No score

Security update for xen

This update for xen fixes the following issues:

Security issues fixed:

  • CVE-2020-11742: Bad continuation handling in GNTTABOP_copy (bsc#1169392).
  • CVE-2020-11740, CVE-2020-11741: xen: XSA-313 multiple xenoprof issues (bsc#1168140).
  • CVE-2020-11739: Missing memory barriers in read-write unlock paths (bsc#1168142).
  • CVE-2020-11743: Bad error path in GNTTABOP_map_grant (bsc#1168143).
  • CVE-2020-7211: Fixed potential directory traversal using relative paths via tftp server on Windows host (bsc#1161181).
  • arm: a CPU may speculate past the ERET instruction (bsc#1160932).

Non-security issues fixed:

  • Xenstored Crashed during VM install (bsc#1167152)
  • DomU hang: soft lockup CPU #0 stuck under high load (bsc#1165206, bsc#1134506)
  • Update API compatibility versions, fixes issues for libvirt. (bsc#1167007, bsc#1157490)
  • aacraid blocks xen commands (bsc#1155200)
Record
SUSE-SU-2020:1138-1
Updated
2026-11-02
OSVSUSE-SU-2020:1139-1 No score

Security update for xen

This update for xen to version 4.12.2 fixes the following issues:

Security issues fixed:

  • CVE-2020-11742: Bad continuation handling in GNTTABOP_copy (bsc#1169392).
  • CVE-2020-11740, CVE-2020-11741: xen: XSA-313 multiple xenoprof issues (bsc#1168140).
  • CVE-2020-11739: Missing memory barriers in read-write unlock paths (bsc#1168142).
  • CVE-2020-11743: Bad error path in GNTTABOP_map_grant (bsc#1168143).
  • CVE-2020-7211: Fixed potential directory traversal using relative paths via tftp server on Windows host (bsc#1161181).
  • arm: a CPU may speculate past the ERET instruction (bsc#1160932).

Non-security issues fixed:

  • Xenstored Crashed during VM install (bsc#1167152)
  • DomU hang: soft lockup CPU #0 stuck under high load (bsc#1165206, bsc#1134506)
  • Update API compatibility versions, fixes issues for libvirt. (bsc#1167007, bsc#1157490)
  • aacraid blocks xen commands (bsc#1155200)
  • Problems Booting Fedora31 VM on sles15 sp1 Xen Dom0 (bsc#1162040).
Record
SUSE-SU-2020:1139-1
Updated
2026-11-02
OSVSUSE-SU-2020:1630-1 No score

Security update for xen

This update for xen fixes the following issues:

  • CVE-2020-0543: Fixed a side channel attack against special registers which could have resulted in leaking of read values to cores other than the one which called it. This attack is known as Special Register Buffer Data Sampling (SRBDS) or 'CrossTalk' (bsc#1172205).
  • CVE-2020-11742: Bad continuation handling in GNTTABOP_copy (bsc#1169392).
  • CVE-2020-11740, CVE-2020-11741: xen: XSA-313 multiple xenoprof issues (bsc#1168140).
  • CVE-2020-11739: Missing memory barriers in read-write unlock paths (bsc#1168142).
  • CVE-2019-19583: Fixed improper checks which could have allowed HVM/PVH guest userspace code to crash the guest, leading to a guest denial of service (bsc#1158004 XSA-308).
  • CVE-2019-19581: Fixed a potential out of bounds on 32-bit Arm (bsc#1158003 XSA-307).
  • CVE-2019-19580: Fixed a privilege escalation where a malicious PV guest administrator could have been able to escalate their privilege to that of the host (bsc#1158006 XSA-310).
  • CVE-2019-19579: Fixed a privilege escalation where an untrusted domain with access to a physical device can DMA into host memory (bsc#1157888 XSA-306).
  • CVE-2019-19578: Fixed an issue where a malicious or buggy PV guest could have caused hypervisor crash resulting in denial of service affecting the entire host (bsc#1158005 XSA-309).
  • CVE-2019-19577: Fixed an issue where a malicious guest administrator could have caused Xen to access data structures while they are being modified leading to a crash (bsc#1158007 XSA-311).
  • Xenstored Crashed during VM install (bsc#1167152)
Record
SUSE-SU-2020:1630-1
Updated
2026-11-02
OSVSUSE-SU-2020:1634-1 No score

Security update for xen

This update for xen fixes the following issues:

  • CVE-2020-0543: Fixed a side channel attack against special registers which could have resulted in leaking of read values to cores other than the one which called it. This attack is known as Special Register Buffer Data Sampling (SRBDS) or 'CrossTalk' (bsc#1172205).
  • CVE-2020-11742: Bad continuation handling in GNTTABOP_copy (bsc#1169392).
  • CVE-2020-11740, CVE-2020-11741: xen: XSA-313 multiple xenoprof issues (bsc#1168140).
  • CVE-2020-11739: Missing memory barriers in read-write unlock paths (bsc#1168142).
  • CVE-2020-11743: Bad error path in GNTTABOP_map_grant (bsc#1168143).
  • Xenstored Crashed during VM install (bsc#1167152)
Record
SUSE-SU-2020:1634-1
Updated
2026-11-02
OSVSUSE-SU-2020:2234-1 No score

Security update for xen

This update for xen fixes the following issues:

  • bsc#1174543 - secure boot related fixes
  • bsc#1163019 - CVE-2020-8608: Potential OOB access due to unsafe snprintf() usages
  • bsc#1169392 - CVE-2020-11742: Bad continuation handling in GNTTABOP_copy
  • bsc#1168140 - CVE-2020-11740, CVE-2020-11741: Multiple xenoprof issues
  • bsc#1168142 - CVE-2020-11739: Missing memory barriers in read-write unlock paths
Record
SUSE-SU-2020:2234-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

Affected packages
PackageAffectedFixed
xen
Alpine:v3.10
 before 4.12.2-r1
4.12.2-r1
xen
Alpine:v3.11
 before 4.13.0-r1
4.13.0-r1
xen
Alpine:v3.12
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.13
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.14
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.15
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.16
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.17
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.18
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.19
 before 4.13.0-r3
4.13.0-r3
Show 39 moreShow less
Affected packages
PackageAffectedFixed
xen
Alpine:v3.20
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.21
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.22
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.23
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.24
 before 4.13.0-r3
4.13.0-r3
xen
Alpine:v3.8
 before 4.10.4-r3
4.10.4-r3
xen
Alpine:v3.9
 before 4.11.3-r2
4.11.3-r2
xen
Debian:12
 before 4.11.4-1
4.11.4-1
xen
Debian:13
 before 4.11.4-1
4.11.4-1
xen
Debian:14
 before 4.11.4-1
4.11.4-1
xen
Debian: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
xen
SUSE:Linux Enterprise Module for Basesystem 15 SP1
From an advisory covering 5 CVEs
 before 4.12.2_04-3.15.1
4.12.2_04-3.15.1
xen
SUSE:Linux Enterprise Module for Server Applications 15 SP1
From an advisory covering 5 CVEs
 before 4.12.2_04-3.15.1
4.12.2_04-3.15.1
xen
SUSE:Linux Enterprise Software Development Kit 12 SP4
From an advisory covering 6 CVEs
 before 4.11.3_04-2.23.1
4.11.3_04-2.23.1
xen
SUSE:Linux Enterprise Server 12 SP4
From an advisory covering 6 CVEs
 before 4.11.3_04-2.23.1
4.11.3_04-2.23.1
xen
SUSE:Linux Enterprise Server for SAP Applications 12 SP4
From an advisory covering 6 CVEs
 before 4.11.3_04-2.23.1
4.11.3_04-2.23.1
xen
SUSE:Linux Enterprise Software Development Kit 12 SP5
From an advisory covering 6 CVEs
 before 4.12.2_04-3.11.1
4.12.2_04-3.11.1
xen
SUSE:Linux Enterprise Server 12 SP5
From an advisory covering 6 CVEs
 before 4.12.2_04-3.11.1
4.12.2_04-3.11.1
xen
SUSE:Linux Enterprise Server for SAP Applications 12 SP5
From an advisory covering 6 CVEs
 before 4.12.2_04-3.11.1
4.12.2_04-3.11.1
xen
SUSE:HPE Helion OpenStack 8
From an advisory covering 12 CVEs
 before 4.9.4_06-3.62.1
4.9.4_06-3.62.1
xen
SUSE:OpenStack Cloud 8
From an advisory covering 12 CVEs
 before 4.9.4_06-3.62.1
4.9.4_06-3.62.1
xen
SUSE:OpenStack Cloud Crowbar 8
From an advisory covering 12 CVEs
 before 4.9.4_06-3.62.1
4.9.4_06-3.62.1
xen
SUSE:Linux Enterprise Server for SAP Applications 12 SP3
From an advisory covering 12 CVEs
 before 4.9.4_06-3.62.1
4.9.4_06-3.62.1
xen
SUSE:Linux Enterprise Server 12 SP3-LTSS
From an advisory covering 12 CVEs
 before 4.9.4_06-3.62.1
4.9.4_06-3.62.1
xen
SUSE:Linux Enterprise Server 12 SP3-BCL
From an advisory covering 12 CVEs
 before 4.9.4_06-3.62.1
4.9.4_06-3.62.1
xen
SUSE:Enterprise Storage 5
From an advisory covering 12 CVEs
 before 4.9.4_06-3.62.1
4.9.4_06-3.62.1
xen
SUSE:Linux Enterprise High Performance Computing 15-ESPOS
From an advisory covering 6 CVEs
 before 4.10.4_10-3.31.1
4.10.4_10-3.31.1
xen
SUSE:Linux Enterprise High Performance Computing 15-LTSS
From an advisory covering 6 CVEs
 before 4.10.4_10-3.31.1
4.10.4_10-3.31.1
xen
SUSE:Linux Enterprise Server for SAP Applications 15
From an advisory covering 6 CVEs
 before 4.10.4_10-3.31.1
4.10.4_10-3.31.1
xen
SUSE:OpenStack Cloud 7
From an advisory covering 5 CVEs
 before 4.7.6_08-43.64.1
4.7.6_08-43.64.1
xen
SUSE:Linux Enterprise Server for SAP Applications 12 SP2
From an advisory covering 5 CVEs
 before 4.7.6_08-43.64.1
4.7.6_08-43.64.1
xen
SUSE:Linux Enterprise Server 12 SP2-LTSS
From an advisory covering 5 CVEs
 before 4.7.6_08-43.64.1
4.7.6_08-43.64.1
xen
SUSE:Linux Enterprise Server 12 SP2-BCL
From an advisory covering 5 CVEs
 before 4.7.6_08-43.64.1
4.7.6_08-43.64.1
xen
Ubuntu: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 less
4.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
xen
Ubuntu:18.04:LTS
 All versions, plus listed versions
4.9.0-0ubuntu34.9.0-0ubuntu44.9.2-0ubuntu1
 None known
xen
Ubuntu: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
xen
Ubuntu: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
xen
openSUSE:Leap 15.1
From an advisory covering 5 CVEs
 before 4.12.2_04-lp151.2.15.1
4.12.2_04-lp151.2.15.1
xen
openSUSE:Tumbleweed
From an advisory covering 93 CVEs
 before 4.15.1_01-1.2
4.15.1_01-1.2

History

History
RecordedChangedSources
affected, facts
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2020-11739 is a high vulnerability (CVSS 7.8) in Xen, published April 14, 2020. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.29%, the 21st percentile. Fixed in xen 4.12.2-r1.

References

Show 163 moreShow less
Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open