CVE-2015-3214: Buffer Overflow

Published Jun 9, 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.

Other sources

The pitioportread in i8254.c in the Linux kernel before 2.6.33 and QEMU before 2.3.1 does not distinguish between read lengths and write lengths, which might allow guest OS users to execute arbitrary code on the host OS by triggering use of an invalid index.

MITRE

Affected Software

51 affected components
Qemu Qemu<=2.3.0
Linux Linux kernel<=2.6.32
Arista EOS=4.12
Arista EOS=4.13
Arista EOS=4.14
Arista EOS=4.15
Debian Debian Linux=7.0
Debian Debian Linux=8.0
Lenovo Emc Px12-400r Ivx<1.0.10.33264
Lenovo Emc Px12-450r Ivx<1.0.10.33264
redhat Openstack=5.0
redhat Openstack=6.0
redhat Virtualization=3.0
redhat Enterprise Linux Compute Node Eus=7.1
redhat Enterprise Linux Compute Node Eus=7.2
redhat Enterprise Linux Compute Node Eus=7.3
redhat Enterprise Linux Compute Node Eus=7.4
redhat Enterprise Linux Compute Node Eus=7.5
redhat Enterprise Linux Compute Node Eus=7.6
redhat 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
redhat Enterprise Linux Server From Rhui=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

Event History

Jun 9, 2015
Data Sourced
10:23 AM
DescriptionSeverityAffected Software
Aug 31, 2015
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2015-3214?

CVE-2015-3214 is classified as a critical vulnerability due to its potential to cause memory corruption.

2

Which software versions are affected by CVE-2015-3214?

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.

3

How do I fix CVE-2015-3214?

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.

4

What are the potential impacts of CVE-2015-3214?

The potential impacts of CVE-2015-3214 include memory corruption and the possibility of system crashes or unstable behavior.

5

Is there a workaround for CVE-2015-3214?

Currently, there is no known workaround for CVE-2015-3214, and updating to a non-vulnerable version is advised.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203