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.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://bugs.launchpad.net/qemu/+bug/1886362 | issue tracking exploit third party advisory |
https://lists.gnu.org/archive/html/qemu-devel/2020-07/msg05304.html | mailing list third party advisory patch |
https://www.openwall.com/lists/oss-security/2020/07/21/3 | mailing list third party advisory patch |
https://lists.debian.org/debian-lts-announce/2021/02/msg00024.html | third party advisory mailing list |
https://security.gentoo.org/glsa/202208-27 | third party advisory vendor advisory |
https://lists.debian.org/debian-lts-announce/2022/09/msg00008.html | third party advisory mailing list |