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
| ||
|
Date: Wed, 16 Nov 2022 17:40:48 +0000 From: Oliver Upton <oliver.upton@...ux.dev> To: Quentin Perret <qperret@...gle.com> Cc: Marc Zyngier <maz@...nel.org>, James Morse <james.morse@....com>, Alexandru Elisei <alexandru.elisei@....com>, Suzuki K Poulose <suzuki.poulose@....com>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will@...nel.org>, Sudeep Holla <sudeep.holla@....com>, Andrew Walbran <qwandor@...gle.com>, linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.linux.dev, kvmarm@...ts.cs.columbia.edu, linux-kernel@...r.kernel.org, kernel-team@...roid.com Subject: Re: [PATCH 03/12] KVM: arm64: Block unsafe FF-A calls from the host On Wed, Nov 16, 2022 at 05:03:26PM +0000, Quentin Perret wrote: > From: Will Deacon <will@...nel.org> > > When KVM is initialised in protected mode, we must take care to filter > certain FFA calls from the host kernel so that the integrity of guest > and hypervisor memory is maintained and is not made available to the > secure world. > > As a first step, intercept and block all memory-related FF-A SMC calls > from the host to EL3. This puts the framework in place for handling them > properly. Shouldn't FFA_FEATURES interception actually precede this patch? At this point in the series we're outright lying about the supported features to the host. -- Thanks, Oliver
Powered by blists - more mailing lists