linux-kernel - Re: [PATCH] xen/arm: do not setup the runstate info page if kpti is enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 30 Sep 2020 10:13:39 -0400
From:   boris.ostrovsky@...cle.com
To:     Stefano Stabellini <sstabellini@...nel.org>,
        linux-kernel@...r.kernel.org
Cc:     Stefano Stabellini <stefano.stabellini@...inx.com>,
        Bertrand Marquis <Bertrand.Marquis@....com>, jgross@...e.com
Subject: Re: [PATCH] xen/arm: do not setup the runstate info page if kpti is
 enabled

On 9/24/20 7:49 PM, Stefano Stabellini wrote:

> From: Stefano Stabellini <stefano.stabellini@...inx.com>
>
> The VCPUOP_register_runstate_memory_area hypercall takes a virtual
> address of a buffer as a parameter. The semantics of the hypercall are
> such that the virtual address should always be valid.
>
> When KPTI is enabled and we are running userspace code, the virtual
> address is not valid, thus, Linux is violating the semantics of
> VCPUOP_register_runstate_memory_area.
>
> Do not call VCPUOP_register_runstate_memory_area when KPTI is enabled.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@...inx.com>
> CC: Bertrand Marquis <Bertrand.Marquis@....com>
> CC: boris.ostrovsky@...cle.com
> CC: jgross@...e.com


Applied to for-linus-5.10



-boris