Last updated 25 August 2025

A heap buffer overflow issue was found in the loaddevicetree() function of QEMU, which is invoked to load device tree blob at boot time. It occurs due to device tree size manipulation before buffer allocation, which could overflow a signed int type.

A user/process could use this flaw to potentially execute arbitrary code on a host system with privileges of the QEMU process.

Upstream patch: --------------- -> https://git.qemu.org/?p=qemu.git;a=commitdiff;h=da885fe1ee8b4589047484bd7fa05a4905b52b17 -> https://git.qemu.org/?p=qemu.git;a=commitdiff;h=065e6298a75164b4347682b63381dbe752c2b156

Reference: ---------- -> https://www.openwall.com/lists/oss-security/2019/03/27/1

Last updated 25 August 2025

hw/rdma/vmw/pvrdmamain.c in QEMU does not implement a read operation (such as uarread by analogy to uarwrite), which allows attackers to cause a denial of service (NULL pointer dereference).

hw/rdma/rdmabackend.c in QEMU allows guest OS users to trigger out-of-bounds access via a PvrdmaSqWqe ring element with a large numsge value.

hw/rdma/vmw/pvrdmacmd.c in QEMU allows attackers to cause a denial of service (NULL pointer dereference or excessive memory allocation) in createcqring or createqprings.

hw/rdma/vmw/pvrdmacmd.c in QEMU allows createcq and createqp memory leaks because errors are mishandled.

Last updated 25 August 2025

A flaw was found in qemu Media Transfer Protocol (MTP). The code opening files in usbmtpgetobject and usbmtpgetpartialobject and directories in usbmtpobjectreaddir doesn't consider that the underlying filesystem may have changed since the time lstat(2) was called in usbmtpobjectalloc, a classical TOCTTOU problem. An attacker with write access to the host filesystem shared with a guest can use this property to navigate the host filesystem in the context of the QEMU process and read any file the QEMU process has access to. Access to the filesystem may be local or via a network share protocol such as CIFS.