CVE-2016-5238: Medium severity Qemu Qemu vulnerability
Quick Emulator(Qemu) built with the ESP/NCR53C9x controller emulation support is vulnerable to an OOB write access issue. The controller uses 16-byte FIFO buffer for command and information transfer. The OOB write occurs while reading from information transfer buffer via non-DMA mode in routine getcmd().
A privileged user inside guest could use this flaw to crash the Qemu process resulting in DoS.
Upstream patch: --------------- -> https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg00150.html
Reference: ---------- -> http://www.openwall.com/lists/oss-security/2016/06/02/9
Other sources
The getcmd function in hw/scsi/esp.c in QEMU might allow local guest OS administrators to cause a denial of service (out-of-bounds write and QEMU process crash) via vectors related to reading from the information transfer buffer in non-DMA mode.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2016-5238?
CVE-2016-5238 is classified as having moderate severity due to the out-of-bounds write access vulnerability.
How do I fix CVE-2016-5238?
To fix CVE-2016-5238, upgrade QEMU to version 2.6.3 or later, which addresses the vulnerability.
What systems are affected by CVE-2016-5238?
CVE-2016-5238 affects QEMU versions up to 2.6.2, as well as specific versions of Ubuntu and Debian Linux.
What kind of vulnerability is CVE-2016-5238?
CVE-2016-5238 is an out-of-bounds write vulnerability that occurs in the command and information transfer routines.
Can CVE-2016-5238 be exploited remotely?
CVE-2016-5238 may be exploitable remotely if an attacker can access the affected QEMU environment.