From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [PATCH 14/24] x86: Restrict MSR access when the kernel is locked down Date: Fri, 14 Apr 2017 20:30:33 +0200 (CEST) Message-ID: References: <149142326734.5101.4596394505987813763.stgit@warthog.procyon.org.uk> <149142339340.5101.1283602261267937893.stgit@warthog.procyon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <149142339340.5101.1283602261267937893.stgit@warthog.procyon.org.uk> Sender: owner-linux-security-module@vger.kernel.org To: David Howells Cc: linux-kernel@vger.kernel.org, matthew.garrett@nebula.com, linux-efi@vger.kernel.org, Kees Cook , gnomes@lxorguk.ukuu.org.uk, gregkh@linuxfoundation.org, x86@kernel.org, linux-security-module@vger.kernel.org, keyrings@vger.kernel.org List-Id: linux-efi@vger.kernel.org On Wed, 5 Apr 2017, David Howells wrote: Can you please change the subsys in $subject to 'x86/msr:' ? > From: Matthew Garrett > > Writing to MSRs should not be allowed if the kernel is locked down, since > it could lead to execution of arbitrary code in kernel mode. Based on a > patch by Kees Cook. > > Signed-off-by: Matthew Garrett > Signed-off-by: David Howells > Acked-by: Kees Cook > cc: x86@kernel.org Reviewed-by: Thomas Gleixner