From: Like Xu <like.xu.linux@gmail.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Liu, Jing2" <jing2.liu@intel.com>,
Wanpeng Li <wanpengli@tencent.com>, "Christopherson,,
Sean" <seanjc@google.com>, Jim Mattson <jmattson@google.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Joerg Roedel <joro@8bytes.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86/cpuid: Exclude unpermitted xfeatures for vcpu->arch.guest_supported_xcr0
Date: Mon, 24 Jan 2022 15:17:39 +0800 [thread overview]
Message-ID: <38c1fbc3-d770-48f3-5432-8fa1fde033f5@gmail.com> (raw)
In-Reply-To: <BN9PR11MB52762E2DEF810DF9AFAE1DDC8C5E9@BN9PR11MB5276.namprd11.prod.outlook.com>
On 24/1/2022 3:06 pm, Tian, Kevin wrote:
>> From: Like Xu <like.xu.linux@gmail.com>
>> Sent: Sunday, January 23, 2022 1:50 PM
>>
>> From: Like Xu <likexu@tencent.com>
>>
>> A malicious user space can bypass xstate_get_guest_group_perm() in the
>> KVM_GET_SUPPORTED_CPUID mechanism and obtain unpermitted xfeatures,
>> since the validity check of xcr0 depends only on guest_supported_xcr0.
>
> Unpermitted xfeatures cannot pass kvm_check_cpuid()...
Indeed, 5ab2f45bba4894a0db4af8567da3efd6228dd010.
This part of logic is pretty fragile and fragmented due to semantic
inconsistencies between supported_xcr0 and guest_supported_xcr0
in other three places:
- __do_cpuid_func
- kvm_mpx_supported
- kvm_vcpu_ioctl_x86_set_xsave
Have you identified all their areas of use ?
>
>>
>> Fixes: 445ecdf79be0 ("kvm: x86: Exclude unpermitted xfeatures at
>> KVM_GET_SUPPORTED_CPUID")
>> Signed-off-by: Like Xu <likexu@tencent.com>
>> ---
>> arch/x86/kvm/cpuid.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/x86/kvm/cpuid.c b/arch/x86/kvm/cpuid.c
>> index 3902c28fb6cb..1bd4d560cbdd 100644
>> --- a/arch/x86/kvm/cpuid.c
>> +++ b/arch/x86/kvm/cpuid.c
>> @@ -266,7 +266,8 @@ static void kvm_vcpu_after_set_cpuid(struct
>> kvm_vcpu *vcpu)
>> vcpu->arch.guest_supported_xcr0 = 0;
>> else
>> vcpu->arch.guest_supported_xcr0 =
>> - (best->eax | ((u64)best->edx << 32)) &
>> supported_xcr0;
>> + (best->eax | ((u64)best->edx << 32)) &
>> + (supported_xcr0 & xstate_get_guest_group_perm());
>>
>> /*
>> * Bits 127:0 of the allowed SECS.ATTRIBUTES (CPUID.0x12.0x1)
>> enumerate
>> --
>> 2.33.1
>
next prev parent reply other threads:[~2022-01-24 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 5:50 Like Xu
2022-01-24 7:06 ` Tian, Kevin
2022-01-24 7:17 ` Like Xu [this message]
2022-01-24 16:23 ` Sean Christopherson
2022-01-24 16:29 ` Paolo Bonzini
2022-01-25 1:54 ` Tian, Kevin
2022-01-25 8:27 ` Paolo Bonzini
2022-01-26 1:23 ` Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38c1fbc3-d770-48f3-5432-8fa1fde033f5@gmail.com \
--to=like.xu.linux@gmail.com \
--cc=jing2.liu@intel.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®