Description of problem: Unprivileged guest callers running in ring 3 can issue, e.g., MMU hypercalls. Normally, such callers cannot provide any hand-crafted MMU command structure as it has to be passed by its physical address, but they can still crash the guest kernel by passing random addresses or access the guest kernel memory, etc. This patch considers hypercalls valid only if issued from guest ring 0. Upstream commit: http://git.kernel.org/linus/07708c4af1346ab1521b26a202f438366b7bcffd CVE request: http://article.gmane.org/gmane.comp.security.oss.general/2130 http://permalink.gmane.org/gmane.comp.security.oss.general/2138 Ref: http://patchwork.kernel.org/patch/38926/
Reproduce in kvm-83-105.el5_4.3 Verified in kvm-83-105.el5_4.5
This issue has been addressed in following products: Red Hat Enterprise Linux 5 Via RHSA-2009:1465 https://rhn.redhat.com/errata/RHSA-2009-1465.html
kernel-2.6.27.35-170.2.94.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/kernel-2.6.27.35-170.2.94.fc10
kernel-2.6.27.35-170.2.94.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.
kernel-2.6.30.9-90.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/kernel-2.6.30.9-90.fc11
kernel-2.6.30.9-90.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.