First published: Tue Jun 09 2015(Updated: )
Due converting PIO to the new memory read/write api we no longer provide separate I/O region lenghts for read and write operations. As a result, reading from PIT Mode/Command register will end with accessing pit->channels with invalid index and potentially cause memory corruption and/or minor information leak. A privileged guest user in a guest with QEMU PIT emulation enabled could potentially (tough unlikely) use this flaw to execute arbitrary code on the host with the privileges of the hosting QEMU process. (QEMU part of the vulnerability) A privileged guest user in a guest could potentially (tough unlikely) use this flaw to execute arbitrary code on the host. (KVM part of the vulnerability) Acknowledgements: Red Hat would like to thank Matt Tait of Google's Project Zero security team for reporting this issue.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
QEMU KVM | <=2.3.0 | |
Linux kernel | <=2.6.32 | |
Arista EOS | =4.12 | |
Arista EOS | =4.13 | |
Arista EOS | =4.14 | |
Arista EOS | =4.15 | |
Debian | =7.0 | |
Debian | =8.0 | |
LenovoEMC px12-400r | <1.0.10.33264 | |
Lenovo EMC px12-450r | <1.0.10.33264 | |
redhat openstack | =5.0 | |
redhat openstack | =6.0 | |
Red Hat Enterprise Virtualization | =3.0 | |
Red Hat Enterprise Linux Compute Node EUS | =7.1 | |
Red Hat Enterprise Linux Compute Node EUS | =7.2 | |
Red Hat Enterprise Linux Compute Node EUS | =7.3 | |
Red Hat Enterprise Linux Compute Node EUS | =7.4 | |
Red Hat Enterprise Linux Compute Node EUS | =7.5 | |
Red Hat Enterprise Linux Compute Node EUS | =7.6 | |
Red Hat Enterprise Linux Compute Node EUS | =7.7 | |
redhat enterprise Linux for power big endian | =7.0 | |
redhat enterprise Linux for power big endian eus | =7.1_ppc64 | |
redhat enterprise Linux for power big endian eus | =7.2_ppc64 | |
redhat enterprise Linux for power big endian eus | =7.3_ppc64 | |
redhat enterprise Linux for power big endian eus | =7.4_ppc64 | |
redhat enterprise Linux for power big endian eus | =7.5_ppc64 | |
redhat enterprise Linux for power big endian eus | =7.6_ppc64 | |
redhat enterprise Linux for power big endian eus | =7.7_ppc64 | |
redhat enterprise Linux for scientific computing | =7.0 | |
redhat enterprise Linux server | =7.0 | |
redhat enterprise Linux server aus | =7.3 | |
redhat enterprise Linux server aus | =7.4 | |
redhat enterprise Linux server aus | =7.6 | |
redhat enterprise Linux server aus | =7.7 | |
redhat enterprise Linux server eus | =7.1 | |
redhat enterprise Linux server eus | =7.2 | |
redhat enterprise Linux server eus | =7.3 | |
redhat enterprise Linux server eus | =7.4 | |
redhat enterprise Linux server eus | =7.5 | |
redhat enterprise Linux server eus | =7.6 | |
redhat enterprise Linux server eus | =7.7 | |
Red Hat Enterprise Linux Server Supplementary EUS | =7.0 | |
redhat enterprise Linux server tus | =7.3 | |
redhat enterprise Linux server tus | =7.6 | |
redhat enterprise Linux server tus | =7.7 | |
redhat enterprise Linux server update services for sap solutions | =7.2 | |
redhat enterprise Linux server update services for sap solutions | =7.3 | |
redhat enterprise Linux server update services for sap solutions | =7.4 | |
redhat enterprise Linux server update services for sap solutions | =7.6 | |
redhat enterprise Linux server update services for sap solutions | =7.7 | |
redhat enterprise Linux workstation | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-3214 is classified as a critical vulnerability due to its potential to cause memory corruption.
CVE-2015-3214 affects multiple versions of QEMU up to 2.3.0, several versions of Linux Kernel up to 2.6.32, and specific versions of Arista EOS and Red Hat software.
To fix CVE-2015-3214, it is recommended to update the affected software to the latest versions provided by the vendor that include security patches.
The potential impacts of CVE-2015-3214 include memory corruption and the possibility of system crashes or unstable behavior.
Currently, there is no known workaround for CVE-2015-3214, and updating to a non-vulnerable version is advised.