First published: Fri Sep 18 2009(Updated: )
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: <a href="http://git.kernel.org/linus/07708c4af1346ab1521b26a202f438366b7bcffd">http://git.kernel.org/linus/07708c4af1346ab1521b26a202f438366b7bcffd</a> CVE request: <a href="http://article.gmane.org/gmane.comp.security.oss.general/2130">http://article.gmane.org/gmane.comp.security.oss.general/2130</a> <a href="http://permalink.gmane.org/gmane.comp.security.oss.general/2138">http://permalink.gmane.org/gmane.comp.security.oss.general/2138</a> Ref: <a href="http://patchwork.kernel.org/patch/38926/">http://patchwork.kernel.org/patch/38926/</a>
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Linux kernel | <=2.6.30 | |
Linux Linux kernel | =2.6.25-rc1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.