A use-after-free flaw was found in libvirt. The qemuMonitorUnregister() function in qemuProcessHandleMonitorEOF is called using multiple threads without being adequately protected by a monitor lock. This flaw could be triggered by the virConnectGetAllDomainStats API when the guest is shutting down. An unprivileged client with a read-only connection could use this flaw to perform a denial of service attack by causing the libvirt daemon to crash.
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libvirt | Redhat | * | 7.1.0 (excluding) |
| Advanced Virtualization for RHEL 8.5.0 | RedHat | virt:av-8050020211025110038.c5368500 | * |
| Advanced Virtualization for RHEL 8.5.0 | RedHat | virt-devel:av-8050020211025110038.c5368500 | * |
| Red Hat Enterprise Linux 8 | RedHat | virt-devel:rhel-8060020220408104655.d63f516d | * |
| Red Hat Enterprise Linux 8 | RedHat | virt:rhel-8060020220408104655.d63f516d | * |
| Libvirt | Ubuntu | bionic | * |
| Libvirt | Ubuntu | devel | * |
| Libvirt | Ubuntu | esm-infra/bionic | * |
| Libvirt | Ubuntu | esm-infra/focal | * |
| Libvirt | Ubuntu | focal | * |
| Libvirt | Ubuntu | hirsute | * |
| Libvirt | Ubuntu | jammy | * |
| Libvirt | Ubuntu | kinetic | * |
| Libvirt | Ubuntu | lunar | * |
| Libvirt | Ubuntu | mantic | * |
| Libvirt | Ubuntu | noble | * |
| Libvirt | Ubuntu | oracular | * |
| Libvirt | Ubuntu | plucky | * |
| Libvirt | Ubuntu | trusty | * |
| Libvirt | Ubuntu | trusty/esm | * |
| Libvirt | Ubuntu | upstream | * |
| Libvirt | Ubuntu | xenial | * |
The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system’s reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:
In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.