From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [kernel-hardening] Re: [PATCH] x86: make IDT read-only Date: Tue, 09 Apr 2013 11:59:15 -0700 Message-ID: <51646503.2010200@zytor.com> References: <20130408224328.GA17641@www.outflux.net> <51634935.9010905@zytor.com> <51645D6F.7070705@zytor.com> <51646054.3090509@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Eric Northup Cc: Alexander Duyck , Alex Shi , Jeremy Fitzhardinge , Will Drewry , Kees Cook , Julien Tinnes , Konrad Rzeszutek Wilk , Frederic Weisbecker , Dan Rosenberg , "x86@kernel.org" , LKML , Steven Rostedt , Borislav Petkov , Ingo Molnar , "kernel-hardening@lists.openwall.com" , "Paul E. McKenney" , "virtualization@lists.linux-foundation.org" , "xen-devel@lists.xensource.com" List-Id: virtualization@lists.linuxfoundation.org On 04/09/2013 11:54 AM, Eric Northup wrote: > > The GDT is a problem if the address returned by 'sgdt' is > kernel-writable - it doesn't necessarily reveal the random offset, but > I'm pretty sure that writing to the GDT could cause privilege > escalation. > That is a pretty safe assumption... -hpa