CVE-2020-13800 json
ati-vga in hw/display/ati.c in QEMU 4.2.0 allows guest OS users to trigger infinite recursion via a crafted mm_index value during an ati_mm…
published 2020-06-04 6 y ago modified 2026-06-17 4 mo ago also EUVD-2020-6015
- cvss
- 6.0
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
ati-vga in hw/display/ati.c in QEMU 4.2.0 allows guest OS users to trigger infinite recursion via a crafted mm_index value during an ati_mm_read or ati_mm_write call.
Patch / fix
- qemu Debian 14, Debian 13, Debian 12 1:5.0-6
debian advisories DEBIAN-CVE-2020-13800
- qemu Ubuntu 20.04 LTS 1:4.2-3ubuntu6.4
ubuntu advisories UBUNTU-CVE-2020-13800
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- qemu SLE Module for Server Applications 15 SP2, SLE Module for Basesystem 15 SP2 4.2.1-11.4.4
suse advisories SUSE-SU-2020:2015-1
- qemu openSUSE Tumbleweed 6.1.0-32.1
- qemu openSUSE Leap 15.2 4.2.1-lp152.9.3.1
- qemu-testsuite openSUSE Leap 15.2 4.2.1-lp152.9.3.1
- qemu-linux-user openSUSE Leap 15.2 4.2.1-lp152.9.3.1
opensuse advisories openSUSE-SU-2024:11287-1openSUSE-SU-2020:1108-1
- qemu Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 5.0.0-r0
alpine advisories ALPINE-CVE-2020-13800
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-13800 updated cvss 2.5
QEMU: ati-vga: infinite recursion in ati_mm_read/write calls may lead to DoS
-
Red Hat Enterprise Linux 5 kvm Red Hat Enterprise Linux 6 qemu-img, qemu-kvm, qemu-kvm-tools, qemu-guest-agent, qemu-guest-agent-win32 Red Hat Enterprise Linux 7 qemu-img, qemu-kvm, libcacard, qemu-img-ma, qemu-kvm-ma, qemu-kvm-rhev, +6 more Red Hat Enterprise Linux 8 qemu-img, qemu-kvm, qemu-kvm-core, qemu-kvm-tests, qemu-kvm-common, qemu-guest-agent, +8 more Red Hat Enterprise Linux 8 Advanced Virtualization qemu-img, qemu-kvm, qemu-kiwi, qemu-kvm-core, qemu-kvm-tests, qemu-kvm-common, +9 more Red Hat Enterprise Linux 9 qemu-img, qemu-kvm, qemu-kvm-core, qemu-kvm-tools, qemu-pr-helper, qemu-kvm-common, +16 morenot affected: vulnerable code not present
+2 more productsfewer
Red Hat OpenStack Platform 10 (Newton) qemu-img-rhev, qemu-kvm-rhev, qemu-kvm-tools-rhev, qemu-kvm-common-rhev Red Hat OpenStack Platform 13 (Queens) qemu-img-rhev, qemu-kvm-rhev, qemu-kvm-tools-rhev, qemu-kvm-common-rhev
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.0 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H |
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
References
-
lists.opensuse.org
/opensuse-security-announce/2020-07/msg00086.html
vendor-advisory, mailing-list, third-party-advisory
-
usn.ubuntu.com
/4467-1/
vendor-advisory, third-party-advisory
-
security.gentoo.org
/glsa/202011-09
vendor-advisory, third-party-advisory
-
lists.gnu.org
/archive/html/qemu-devel/2020-06/msg00825.html
mailing-list, vendor-advisory
-
openwall.com
/lists/oss-security/2020/06/04/2
mailing-list, third-party-advisory
-
security.netapp.com
/advisory/ntap-20200717-0001/
third-party-advisory
-
cve.openeuler.org
/cve#/CVEInfo/CVE-2020-13800
broken-link
Sources
- CVE List CVE-2020-13800
- NVD CVE-2020-13800
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.