Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 526837

Summary: KVM: x86: verify MTRR/PAT validity (upstream backport)
Product: Red Hat Enterprise Linux 5 Reporter: Marcelo Tosatti <mtosatti>
Component: kvmAssignee: Eduardo Habkost <ehabkost>
Status: CLOSED ERRATA QA Contact: Lawrence Lim <llim>
Severity: medium Docs Contact:
Priority: high    
Version: 5.4.zCC: cpelland, lihuang, tburke, tools-bugs, virt-maint, ykaul
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: kvm-83-124.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-30 07:53:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 552520    
Attachments:
Description Flags
KVM-verify-MTRR-validity.patch none

Description Marcelo Tosatti 2009-10-02 00:00:04 UTC
Created attachment 363407 [details]
KVM-verify-MTRR-validity.patch

Do not allow invalid memory types in MTRR/PAT (generating a #GP
otherwise).

Signed-off-by: Marcelo Tosatti <mtosatti>
Signed-off-by: Avi Kivity <avi>
(cherry picked from commit d6289b9365c3f622a8cfe62c4fb054bb70b5061a)

This is important to avoid guests running random code to possibly store (and later use) a random MTRR type.

Comment 14 errata-xmlrpc 2010-03-30 07:53:17 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0271.html