First published: Thu Jul 29 2010(Updated: )
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: <a href="http://www.spinics.net/lists/kvm/msg39173.html">http://www.spinics.net/lists/kvm/msg39173.html</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Enterprise Virtualization | =2.2 | |
Red Hat KVM | =83 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-2784 has a severity rating of medium due to the potential for segmentation faults.
To fix CVE-2010-2784, you should update to the latest version of the affected software as per the vendor's security advisories.
The impact of CVE-2010-2784 includes possible application crashes and denial of service due to segmentation faults.
CVE-2010-2784 affects Red Hat Enterprise Virtualization 2.2 and Red Hat KVM 83.
Mitigation strategies for CVE-2010-2784 include monitoring for abnormal application behavior and applying the necessary updates promptly.