A flaw was found in QEMU. The async nature of hot-unplug enables a race scenario where the net device backend is cleared before the virtio-net pci frontend has been unplugged. A malicious guest could use this time window to trigger an assertion and cause a denial of service.
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Qemu | Qemu | * | 8.0.3 (including) |
| Red Hat Enterprise Linux 8 | RedHat | virt-devel:rhel-8090020230927071820.b46abd14 | * |
| Red Hat Enterprise Linux 8 | RedHat | virt:rhel-8090020230927071820.b46abd14 | * |
| Qemu | Ubuntu | bionic | * |
| Qemu | Ubuntu | jammy | * |
| Qemu | Ubuntu | lunar | * |
| Qemu | Ubuntu | trusty | * |
| Qemu | Ubuntu | upstream | * |
| Qemu | Ubuntu | xenial | * |
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, it can still lead to a denial of service. For example, if a server handles multiple simultaneous connections, and an assert() occurs in one single connection that causes all other connections to be dropped, this is a reachable assertion that leads to a denial of service.