Re: [PATCH v5 1/4] syscalls: Restore address limit after a syscall

2017-03-31 Thread Thomas Garnier
On Thu, Mar 23, 2017 at 1:15 PM, Kees Cook wrote: > On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote: >> This patch ensures a syscall does not return to user-mode with a kernel >> address limit. If that happened, a process can corrupt kernel-mode

Re: [PATCH v5 1/4] syscalls: Restore address limit after a syscall

2017-03-31 Thread Thomas Garnier
On Thu, Mar 23, 2017 at 1:15 PM, Kees Cook wrote: > On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote: >> This patch ensures a syscall does not return to user-mode with a kernel >> address limit. If that happened, a process can corrupt kernel-mode >> memory and elevate privileges. >> >> For

Re: [PATCH v5 1/4] syscalls: Restore address limit after a syscall

2017-03-23 Thread Kees Cook
On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote: > This patch ensures a syscall does not return to user-mode with a kernel > address limit. If that happened, a process can corrupt kernel-mode > memory and elevate privileges. > > For example, it would mitigation this

Re: [PATCH v5 1/4] syscalls: Restore address limit after a syscall

2017-03-23 Thread Kees Cook
On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote: > This patch ensures a syscall does not return to user-mode with a kernel > address limit. If that happened, a process can corrupt kernel-mode > memory and elevate privileges. > > For example, it would mitigation this bug: > > -

[PATCH v5 1/4] syscalls: Restore address limit after a syscall

2017-03-23 Thread Thomas Garnier
This patch ensures a syscall does not return to user-mode with a kernel address limit. If that happened, a process can corrupt kernel-mode memory and elevate privileges. For example, it would mitigation this bug: - https://bugs.chromium.org/p/project-zero/issues/detail?id=990 The

[PATCH v5 1/4] syscalls: Restore address limit after a syscall

2017-03-23 Thread Thomas Garnier
This patch ensures a syscall does not return to user-mode with a kernel address limit. If that happened, a process can corrupt kernel-mode memory and elevate privileges. For example, it would mitigation this bug: - https://bugs.chromium.org/p/project-zero/issues/detail?id=990 The