A flaw was found in the libvirt libxl driver. A malicious guest could continuously reboot itself and cause libvirtd on the host to deadlock or crash, resulting in a denial of service condition.
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libvirt | Redhat | * | 2.33.0 (excluding) |
| Libvirt | Ubuntu | bionic | * |
| Libvirt | Ubuntu | focal | * |
| Libvirt | Ubuntu | hirsute | * |
| Libvirt | Ubuntu | impish | * |
| Libvirt | Ubuntu | trusty | * |
| Libvirt | Ubuntu | upstream | * |
| Libvirt | Ubuntu | xenial | * |
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.