| commit | 3f1538a4dd00709b1c7f6a4fda31cf5daf4b3e46 | |
| author | Jan Kiszka <jan.kiszka@siemens.com> | |
| Fri, 18 Sep 2009 23:08:02 +0000 (18 20:08 -0300) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Mon, 5 Oct 2009 15:27:54 +0000 (5 08:27 -0700) | ||
| tree | 875f6eaae8d7f8cc579f64e1b98b35c4b1dd0096 | treesnapshot (tar.gz zip) |
| parent | 0af8b3ad950ea4687cfee0cc5e7af9d941fd02ff | commitdiff |
KVM: x86: Disallow hypercalls for guest callers in rings > 0
(cherry picked from commit 07708c4af1346ab1521b26a202f438366b7bcffd)
So far 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.
To close the hole, this patch considers hypercalls valid only if issued
from guest ring 0. This may still be relaxed on a per-hypercall base in
the future once required.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
(cherry picked from commit 07708c4af1346ab1521b26a202f438366b7bcffd)
So far 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.
To close the hole, this patch considers hypercalls valid only if issued
from guest ring 0. This may still be relaxed on a per-hypercall base in
the future once required.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| arch/x86/kvm/x86.c | diffblobblamehistory | |
| include/linux/kvm_para.h | diffblobblamehistory |