CVE-2011-1751: Input Validation

Published Apr 26, 2011
·
Updated

The pciejwrite function in hw/acpipiix4.c in the PIIX4 Power Management emulation in qemu-kvm does not check if a device is hotpluggable before unplugging the PCI-ISA bridge, which allows privileged guest users to cause a denial of service (guest crash) and possibly execute arbitrary code by sending a crafted value to the 0xae08 (PCIEJBASE) I/O port, which leads to a use-after-free related to "active qemu timers."

Other sources

Writing the value 2 to I/O port 0xae08 ("PCIEJBASE") initiates the PIIX3 PCI-ISA bridge removal. Unplugging this causes all of the ISA devices to be unplugged and right now the ISA (in particularly the RTC) devices cannot handle unplug gracefuly.

During MC146818 removal RTCState structure backing the emulated RTC is freed but embedded timers are not unlinked from activetimers list. Next time the timer fires SIGSEGV occurs. RTCState embedds several QEMUTimer structures that define function pointers (callbacks) that get called when timer expires.

Since the memory is freed, however, it is possible, under some circumstances, for the guest to cause a controlled allocation into the freed space, which can ultimately be exploited for code execution in the context of the qemu or qemu-kvm process.

ASLR partially mitigates this issue.

Acknowledgements:

Red Hat would like to thank Nelson Elhage for reporting this issue.

Red Hat

Affected Software

74 affected components
Qemu Qemu=1.0-rc1
Qemu Qemu=0.12.2
Qemu Qemu=0.12.0-rc2
Qemu Qemu=1.1-rc3
Qemu Qemu=0.1.6
Qemu Qemu=0.13.0-rc0
Qemu Qemu=0.5.3
Qemu Qemu=0.4.2
Qemu Qemu=1.0-rc2
Qemu Qemu=0.10.3
Qemu Qemu=0.11.0-rc1
Qemu Qemu=0.1.5
Qemu Qemu=0.13.0
Qemu Qemu=0.5.1
Qemu Qemu=0.8.2
Qemu Qemu=0.11.0-rc1
Qemu Qemu=1.1-rc4
Qemu Qemu=0.5.5
Qemu Qemu=0.10.1
Qemu Qemu=0.9.0
Qemu Qemu=1.0
Qemu Qemu=1.1-rc2
Qemu Qemu=0.7.2
Qemu Qemu=0.11.0-rc2
Qemu Qemu=0.12.5
Qemu Qemu=0.11.0
Qemu Qemu=0.1.3
Qemu Qemu=0.14.0-rc0
Qemu Qemu=0.12.0-rc1
Qemu Qemu=0.11.1
Qemu Qemu=0.7.1
Qemu Qemu=0.9.1-5
Qemu Qemu=1.0.1
Qemu Qemu=1.0-rc3
Qemu Qemu=0.13.0-rc1
Qemu Qemu=0.15.0-rc1
Qemu Qemu=0.5.0
Qemu Qemu=0.12.0
Qemu Qemu=0.14.1
Qemu Qemu=0.8.1
Qemu Qemu=0.11.0-rc2
Qemu Qemu=0.10.0
Qemu Qemu=0.4.1
Qemu Qemu=0.5.2
Qemu Qemu=0.12.3
Qemu Qemu=0.1.1
Qemu Qemu=0.7.0
Qemu Qemu=0.11.0-rc0
Qemu Qemu=0.1.4
Qemu Qemu=0.9.1
Qemu Qemu=0.6.0
Qemu Qemu=0.6.1
Qemu Qemu=0.14.0-rc2
Qemu Qemu=0.10.6
Qemu Qemu=0.14.0-rc1
Qemu Qemu=0.14.0
Qemu Qemu=0.11.0-rc0
Qemu Qemu=0.4.3
Qemu Qemu=0.1.2
Qemu Qemu=0.5.4
Qemu Qemu=0.12.4
Qemu Qemu=0.10.5
Qemu Qemu=1.0-rc4
Qemu Qemu=0.10.4
Qemu Qemu=0.10.2
Qemu Qemu=0.15.0-rc2
Qemu Qemu=1.1-rc1
Qemu Qemu=1.1
Qemu Qemu=0.12.1
Qemu Qemu=0.8.0
Qemu Qemu=0.1.0
Qemu Qemu=0.2.0
Qemu Qemu=0.3.0
Qemu Qemu=0.4.0

Event History

Apr 26, 2011
Data Sourced
03:26 PM
DescriptionSeverityAffected Software
Jun 21, 2012
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2011-1751?

CVE-2011-1751 has a medium severity rating due to the potential for a denial of service and possible arbitrary code execution.

2

How do I fix CVE-2011-1751?

To fix CVE-2011-1751, update to a patched version of QEMU KVM that addresses the hotplugging vulnerability.

3

Who is affected by CVE-2011-1751?

CVE-2011-1751 affects privileged guest users running certain versions of QEMU KVM that lack proper device checks.

4

What vulnerabilities does CVE-2011-1751 represent?

CVE-2011-1751 represents a vulnerability in the PIIX4 Power Management emulation of QEMU that can lead to guest crashes.

5

What types of systems are impacted by CVE-2011-1751?

CVE-2011-1751 impacts systems using QEMU KVM versions including 0.1.0 through 1.1-rc4.

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