Re: [patch 27/60] x86/cpufeatures: Add X86_BUG_CPU_INSECURE

2017-12-04 Thread Borislav Petkov
On Mon, Dec 04, 2017 at 03:07:33PM +0100, Thomas Gleixner wrote: > From: Thomas Gleixner > > Many x86 CPUs leak information to user space due to missing isolation of > user space and kernel space page tables. There are many well documented > ways to exploit that. > > The

Re: [patch 27/60] x86/cpufeatures: Add X86_BUG_CPU_INSECURE

2017-12-04 Thread Borislav Petkov
On Mon, Dec 04, 2017 at 03:07:33PM +0100, Thomas Gleixner wrote: > From: Thomas Gleixner > > Many x86 CPUs leak information to user space due to missing isolation of > user space and kernel space page tables. There are many well documented > ways to exploit that. > > The upcoming software

[patch 27/60] x86/cpufeatures: Add X86_BUG_CPU_INSECURE

2017-12-04 Thread Thomas Gleixner
From: Thomas Gleixner Many x86 CPUs leak information to user space due to missing isolation of user space and kernel space page tables. There are many well documented ways to exploit that. The upcoming software migitation of isolating the user and kernel space page tables

[patch 27/60] x86/cpufeatures: Add X86_BUG_CPU_INSECURE

2017-12-04 Thread Thomas Gleixner
From: Thomas Gleixner Many x86 CPUs leak information to user space due to missing isolation of user space and kernel space page tables. There are many well documented ways to exploit that. The upcoming software migitation of isolating the user and kernel space page tables needs a misfeature