Re: [kernel-hardening] [PATCH v5 13/32] x86/mm/64: In vmalloc_fault(), use CR3 instead of current->active_mm
From: Dave Hansen
Date: Tue Jul 12 2016 - 13:53:06 EST
On 07/11/2016 01:53 PM, Andy Lutomirski wrote:
> If we get a vmalloc fault while current->active_mm->pgd doesn't
> match CR3, we'll crash without this change. I've seen this failure
> mode on heavily instrumented kernels with virtually mapped stacks.
When does this happen, btw? Crossing page boundaries on the stack
between the time we swap mm's and the time we switch stacks?