First published: Wed Dec 22 2021(Updated: )
A NULL pointer dereference was found in the ACPI code of QEMU. The flaw lies in hw/acpi/pcihp.c in pci_write() where the `bus` pointer is used without checking if it's NULL, probably because an invalid selector was supplied. A malicious privileged user within the guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition. Upstream issue: <a href="https://gitlab.com/qemu-project/qemu/-/issues/770">https://gitlab.com/qemu-project/qemu/-/issues/770</a> Upstream patch: <a href="https://lists.nongnu.org/archive/html/qemu-devel/2021-12/msg01491.html">https://lists.nongnu.org/archive/html/qemu-devel/2021-12/msg01491.html</a>
Affected Software | Affected Version | How to fix |
---|---|---|
QEMU |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-2035002 is classified as critical due to the potential for a malicious privileged user to crash the system.
To fix REDHAT-BUG-2035002, update to the latest version of QEMU that addresses this NULL pointer dereference vulnerability.
REDHAT-BUG-2035002 is caused by a NULL pointer dereference in the ACPI code of QEMU when the `bus` pointer is used without validation.
Users running vulnerable versions of QEMU, especially within a guest environment, are affected by REDHAT-BUG-2035002.
Yes, a malicious privileged user within the guest can exploit REDHAT-BUG-2035002 to crash the QEMU instance.