CVE-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 address. Reporting because I'm not confident about the accuracy of the version in the CVE description. Maintainers, please confirm if we are vulnerable and if so create a patched version. There is a patch on qemu-devel: https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05895.html
5.0 is probably affected as well. Given that it's a very delicate piece of NIC's MMIO emulation we'll wait on fix to land upstream.
(In reply to John Helmert III (ajak) from comment #0) > CVE-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 address. > > > > Reporting because I'm not confident about the accuracy of the version in the > CVE description. Maintainers, please confirm if we are vulnerable and if so > create a patched version. There is a patch on qemu-devel: > > https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05895.html No patch for this yet as far as I can tell, but we have another vulnerability that is patched for 5.1.0-rc1. CVE-2020-15863: hw/net/xgmac.c in the XGMAC Ethernet controller in QEMU before 07-20-2020 has a buffer overflow. This occurs during packet transmission and affects the highbank and midway emulated machines. A guest user or process could use this flaw to crash the QEMU process on the host, resulting in a denial of service or potential privileged code execution. This was fixed in commit 5519724a13664b43e225ca05351c60b4468e4555. Patch: https://git.qemu.org/?p=qemu.git;a=commitdiff;h=5519724a13664b43e225ca05351c60b4468e4555 qemu $ git tag --contains 5519724a13664b43e225ca05351c60b4468e4555 v5.1.0-rc1
(In reply to John Helmert III (ajak) from comment #2) > (In reply to John Helmert III (ajak) from comment #0) > > CVE-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 address. > > > > > > > > Reporting because I'm not confident about the accuracy of the version in the > > CVE description. Maintainers, please confirm if we are vulnerable and if so > > create a patched version. There is a patch on qemu-devel: > > > > https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05895.html I would be surprised if this is still unfixed, but I can't find where/if it made its way into git.
Upstream bug report is still open.
This has still not been resolved upstream.
Fixed "a few months ago" according to upstream, not sure about fixed versions...