CVE-2020-15859
published 2020-07-21CVE-2020-15859: QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO…
PriorityP410low3.3CVSS 3.1
AVLACLPRLUINSUCNINAL
EPSS
0.44%
35.2th percentile
QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| debian | qemu | < qemu 1:5.2+dfsg-1 (bookworm) | qemu 1:5.2+dfsg-1 (bookworm) |
| msrc | cbl_mariner_1.0_arm | — | — |
| msrc | cbl_mariner_1.0_x64 | — | — |
| msrc | cm1_qemu-kvm_4.2.0-21_on_cbl_mariner_1.0 | — | — |
| qemu | qemu | — | — |
| qemu | qemu | >= 0 < 1:5.2+dfsg-1 | 1:5.2+dfsg-1 |
| qemu | qemu | >= 0 < 1:5.2+dfsg-1 | 1:5.2+dfsg-1 |
| qemu | qemu | >= 0 < 1:5.2+dfsg-1 | 1:5.2+dfsg-1 |
| qemu | qemu | >= 0 < 1:5.2+dfsg-1 | 1:5.2+dfsg-1 |
| qemu | qemu | >= 0 < 1:2.5+dfsg-5ubuntu10.49 | 1:2.5+dfsg-5ubuntu10.49 |
| qemu | qemu | >= 0 < 1:2.11+dfsg-1ubuntu7.35 | 1:2.11+dfsg-1ubuntu7.35 |
| qemu | qemu | >= 0 < 1:4.2-3ubuntu6.12 | 1:4.2-3ubuntu6.12 |
| ubuntu | qemu | — | — |
CVSS provenance
nvdv3.13.3LOWCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
nvdv2.02.1LOWAV:L/AC:L/Au:N/C:N/I:N/A:P
osv3.8LOW
vendor_ubuntu3.8LOW
vendor_debian3.3LOW
vendor_msrc3.3LOW
vendor_redhat3.3LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
QEMU regression
vendor_ubuntu·2026-06-28·CVSS 3.8
CVE-2020-11947 [LOW] QEMU regression
Title: QEMU regression
Summary: USN-8412-1 introduced a regression in QEMU
USN-8412-1 fixed vulnerabilities QEMU. On Ubuntu 20.04 LTS, the fix for
CVE-2024-4467 was incomplete and prevented the creation of boot volumes
from qcow2 images. This update fixes the problem.
We apologize for the inconvenience.
Original advisory details:
Felipe Franciosi, Raphael Norwitz, and Peter Turschmid discovered that the
iSCSI block driver in QEMU incorrectly handled certain responses from an
iSCSI server. A remote attacker could possibly use this issue to cause
QEMU to crash, resulting in a denial of service, or possibly execute
arbitrary code. This issue only affected Ubuntu 14.04 LTS. (CVE-2020-1711)
It was discovered that the iSCSI block driver in QEMU incorrectly handled
certain memory operations
Ubuntu
QEMU vulnerabilities
vendor_ubuntu·2026-06-09·CVSS 3.8
CVE-2021-3416 [LOW] QEMU vulnerabilities
Title: QEMU vulnerabilities
Summary: Several security issues were fixed in QEMU.
Felipe Franciosi, Raphael Norwitz, and Peter Turschmid discovered that the
iSCSI block driver in QEMU incorrectly handled certain responses from an
iSCSI server. A remote attacker could possibly use this issue to cause QEMU
to crash, resulting in a denial of service, or possibly execute arbitrary
code. This issue only affected Ubuntu 14.04 LTS. (CVE-2020-1711)
It was discovered that the iSCSI block driver in QEMU incorrectly handled
certain memory operations, leading to a heap-based buffer over-read. An
attacker could possibly use this issue to expose sensitive information from
the host. This issue only affected Ubuntu 14.04 LTS. (CVE-2020-11947)
Ziming Zhang discovered that the SM501 display driver in QEM
Ubuntu
QEMU vulnerabilities
vendor_ubuntu·2021-02-08·CVSS 3.8
CVE-2020-15859 [LOW] QEMU vulnerabilities
Title: QEMU vulnerabilities
Summary: Several security issues were fixed in QEMU.
It was discovered that QEMU incorrectly handled memory in iSCSI emulation.
An attacker inside the guest could possibly use this issue to obtain
sensitive information. This issue only affected Ubuntu 16.04 LTS, Ubuntu
18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2020-11947)
Alexander Bulekov discovered that QEMU incorrectly handled Intel e1000e
emulation. An attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service. (CVE-2020-15859)
Alexander Bulekov discovered that QEMU incorrectly handled memory region
cache. An attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. This issue only affected Ubuntu
20.04 LTS, and Ubunt
Red Hat
QEMU: net: e1000e: use-after-free while sending packets
vendor_redhat·2020-07-16·CVSS 3.3
CVE-2020-15859 [LOW] CWE-416 QEMU: net: e1000e: use-after-free while sending packets
QEMU: net: e1000e: use-after-free while sending packets
QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
A use-after-free flaw was found in the INTEL 82574 NIC (e1000e) emulator of the QEMU. The issue happens while sending packets if the guest user has set the packet data address to the e1000e's MMIO address. This flaw allows a guest user or process to crash the QEMU process on the host, resulting in a denial of service.
Statement: In Red Hat OpenStack Platform, because the flaw has a lower impact and the fix would require a substantial amount of development, no update will be provided at this time for the RHOSP qemu-kvm-rhev package.
Package: kvm (Red Hat Enterprise Li
Microsoft
QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
vendor_msrc·2020-07-14·CVSS 3.3
CVE-2020-15859 [LOW] CWE-416 QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Ma
Debian
CVE-2020-15859: qemu - QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user ...
vendor_debian·2020·CVSS 3.3
CVE-2020-15859 [LOW] CVE-2020-15859: qemu - QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user ...
QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
Scope: local
bookworm: resolved (fixed in 1:5.2+dfsg-1)
bullseye: resolved (fixed in 1:5.2+dfsg-1)
forky: resolved (fixed in 1:5.2+dfsg-1)
sid: resolved (fixed in 1:5.2+dfsg-1)
trixie: resolved (fixed in 1:5.2+dfsg-1)
GHSA
GHSA-xvx4-fr25-r858: QEMU 4
ghsa_unreviewed·2022-05-24
CVE-2020-15859 [LOW] CWE-416 GHSA-xvx4-fr25-r858: QEMU 4
QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
OSV
qemu vulnerabilities
osv·2021-02-08·CVSS 3.8
CVE-2020-11947 [LOW] qemu vulnerabilities
qemu vulnerabilities
It was discovered that QEMU incorrectly handled memory in iSCSI emulation.
An attacker inside the guest could possibly use this issue to obtain
sensitive information. This issue only affected Ubuntu 16.04 LTS, Ubuntu
18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2020-11947)
Alexander Bulekov discovered that QEMU incorrectly handled Intel e1000e
emulation. An attacker inside the guest could use this issue to cause QEMU
to crash, resulting in a denial of service. (CVE-2020-15859)
Alexander Bulekov discovered that QEMU incorrectly handled memory region
cache. An attacker inside the guest could use this issue to cause QEMU to
crash, resulting in a denial of service. This issue only affected Ubuntu
20.04 LTS, and Ubuntu 20.10. (CVE-2020-27821)
Cheol-woo Myung discovered that QE
OSV
CVE-2020-15859: QEMU 4
osv·2020-07-21·CVSS 3.3
CVE-2020-15859 [LOW] CVE-2020-15859: QEMU 4
QEMU 4.2.0 has a use-after-free in hw/net/e1000e_core.c because a guest OS user can trigger an e1000e packet with the data's address set to the e1000e's MMIO address.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-15859 qemu: net: e1000e: use-after-free while sending packets [fedora-all]
bugzilla·2020-07-21·CVSS 3.3
CVE-2020-15859 [LOW] CVE-2020-15859 qemu: net: e1000e: use-after-free while sending packets [fedora-all]
CVE-2020-15859 qemu: net: e1000e: use-after-free while sending packets [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported ve
Bugzilla
CVE-2020-15859 QEMU: net: e1000e: use-after-free while sending packets
bugzilla·2020-07-21·CVSS 3.3
CVE-2020-15859 [LOW] CVE-2020-15859 QEMU: net: e1000e: use-after-free while sending packets
CVE-2020-15859 QEMU: net: e1000e: use-after-free while sending packets
A use-after-free issue was found in the INTEL 82574 NIC (e1000e) emulator of the QEMU.
It could while sending packets if the guest user set the packet data address to
e1000e's MMIO address. A guest user/process could use this flaw to crash the QEMU
process on the host resulting in DoS scenario.
Upstream patch:
-> https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg06147.html
Reference:
-> https://bugs.launchpad.net/qemu/+bug/1886362
Discussion:
Acknowledgments:
Name: Alexander Bulekov
---
Created qemu tracking bugs for this issue:
Affects: fedora-all [bug 1859169]
---
External References:
https://www.openwall.com/lists/oss-security/2020/07/21/3
---
Statement:
In Red Hat OpenStack Platform, because th
https://bugs.launchpad.net/qemu/+bug/1886362https://lists.debian.org/debian-lts-announce/2021/02/msg00024.htmlhttps://lists.debian.org/debian-lts-announce/2022/09/msg00008.htmlhttps://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05304.htmlhttps://security.gentoo.org/glsa/202208-27https://www.openwall.com/lists/oss-security/2020/07/21/3https://bugs.launchpad.net/qemu/+bug/1886362https://lists.debian.org/debian-lts-announce/2021/02/msg00024.htmlhttps://lists.debian.org/debian-lts-announce/2022/09/msg00008.htmlhttps://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05304.htmlhttps://security.gentoo.org/glsa/202208-27https://www.openwall.com/lists/oss-security/2020/07/21/3
2020-07-21
Published