linux-kernel - Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling under SEV-ES

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 28 Oct 2020 10:49:52 +0100
From:   Joerg Roedel <jroedel@...e.de>
To:     Erdem Aktas <erdemaktas@...gle.com>
Cc:     linux-kernel@...r.kernel.org,
        "Lendacky, Thomas" <Thomas.Lendacky@....com>,
        linux-tip-commits@...r.kernel.org, Borislav Petkov <bp@...e.de>,
        x86 <x86@...nel.org>
Subject: Re: [tip: x86/seves] x86/kvm: Add KVM-specific VMMCALL handling
 under SEV-ES

On Tue, Oct 27, 2020 at 04:14:15PM -0700, Erdem Aktas wrote:
> It seems to me that the kvm_sev_es_hcall_prepare is leaking more
> information than it is needed. Is this an expected behavior?

What exactly is leaked? The kvm hypercall uses RAX, RBX, RCX, RDX and
RSI for parameters.

Regards,

	Joerg