Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 26 Oct 2017 15:34:38 +0100
From: Marc Zyngier <>
To: Paolo Bonzini <>
Cc:,,  Christoffer Dall
 <>,  Christian Borntraeger
 <>,  Cornelia Huck <>,  James Hogan
 <>,  Paul Mackerras <>,,  Kees Cook <>,
  Christian Borntraeger <>,  Christoffer Dall
 <>,  Radim Krčmář <>
Subject: Re: [PATCH 1/2] kvm: whitelist struct kvm_vcpu_arch

On Thu, Oct 26 2017 at  3:45:46 pm BST, Paolo Bonzini <> wrote:
> On x86, ARM and s390, struct kvm_vcpu_arch has a usercopy region
> taht is read and written by the KVM_GET/SET_CPUID2 ioctls (x86)
> or KVM_GET/SET_ONE_REG (ARM/s390).  Without whitelisting the area,
> KVM is completely broken on those architectures with usercopy hardening
> enabled.
> For now, allow writing to the entire struct on all architectures.
> The KVM tree will not refine this to an architecture-specific
> subset of struct kvm_vcpu_arch.
> Cc:
> Cc: Kees Cook <>
> Cc: Christian Borntraeger <>
> Cc: Christoffer Dall <>
> Cc: Radim Krčmář <>
> Signed-off-by: Paolo Bonzini <>

Acked-by: Marc Zyngier <>

Jazz is not dead. It just smells funny.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.