Bug 572971 - (CVE-2010-0730) CVE-2010-0730 xen: emulator instruction decoding inconsistency
CVE-2010-0730 xen: emulator instruction decoding inconsistency
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Security
Depends On: 572979 572982
  Show dependency treegraph
Reported: 2010-03-12 09:07 EST by Petr Matousek
Modified: 2015-02-16 10:51 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-04-05 15:59:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Petr Matousek 2010-03-12 09:07:43 EST
Paolo Bonzini found a bug in Xen hypervisor that can be used to crash the guest. Malicious guest userspace process can trick the hypervisor into emulating instruction that causes the crash if it has access to an MMIO region. The bug can be exploited because of an inconsistency between instruction decoding tables and the actual MMIO instruction decoder implementation.
Comment 14 Eugene Teo (Security Response) 2010-04-20 21:49:02 EDT
This issue does not affect upstream.
Comment 15 Petr Matousek 2010-04-27 12:27:19 EDT
This issue affects 32bit guests only.
Comment 18 Josh Bressers 2010-05-06 13:43:20 EDT
Lifting embargo
Comment 19 errata-xmlrpc 2010-05-06 14:49:48 EDT
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2010:0398 https://rhn.redhat.com/errata/RHSA-2010-0398.html
Comment 20 Jarod Wilson 2010-05-19 15:00:33 EDT
in kernel-2.6.18-199.el5
You can download this test kernel from http://people.redhat.com/jwilson/el5

Please update the appropriate value in the Verified field
(cf_verified) to indicate this fix has been successfully
verified. Include a comment with verification details.

Note You need to log in before you can comment on or make changes to this bug.