Bug 619411 - (CVE-2010-2784) CVE-2010-2784 qemu: insufficient constraints checking in exec.c:subpage_register()
CVE-2010-2784 qemu: insufficient constraints checking in exec.c:subpage_regis...
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
public=20100728,reported=20100728,sou...
: Security
Depends On: 619412 619413 619414 619418 619421
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-29 09:47 EDT by Petr Matousek
Modified: 2015-10-15 17:14 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-02 13:04:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Petr Matousek 2010-07-29 09:47:22 EDT
Description of the problem:
It is possible that subpage mmio is registered over existing memory page. When this happens "memory" will have real memory address and not index into io_mem array so next access to the page will generate segfault. It is uncommon to have some part of a page to be accessed as memory and some as mmio, but qemu shouldn't crash even when guest does stupid things. So lets just pretend that the rest of the page is unassigned if guest configure part of the memory page as mmio.

Public post:
http://www.spinics.net/lists/kvm/msg39173.html
Comment 5 errata-xmlrpc 2010-08-19 17:31:56 EDT
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2010:0627 https://rhn.redhat.com/errata/RHSA-2010-0627.html
Comment 6 errata-xmlrpc 2010-08-19 17:45:42 EDT
This issue has been addressed in following products:

  Red Hat Enterprise Virtualization for RHEL-5

Via RHSA-2010:0622 https://rhn.redhat.com/errata/RHSA-2010-0622.html

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