x86/fault: Don't look for extable entries for SMEP violations

If the kernel gets a SMEP violation or a fault that would have been a
SMEP violation if it had SMEP support, it shouldn't run fixups. Just
OOPS.

 [ bp: Massage commit message. ]

Signed-off-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/46160d8babce2abf1d6daa052146002efa24ac56.1612924255.git.luto@kernel.org
This commit is contained in:
Andy Lutomirski 2021-02-09 18:33:44 -08:00 committed by Borislav Petkov
parent 6456a2a69e
commit 66fcd98883
1 changed files with 2 additions and 2 deletions

View File

@ -1250,12 +1250,12 @@ void do_user_addr_fault(struct pt_regs *regs,
* user memory. Unless this is AMD erratum #93, which
* corrupts RIP such that it looks like a user address,
* this is unrecoverable. Don't even try to look up the
* VMA.
* VMA or look for extable entries.
*/
if (is_errata93(regs, address))
return;
bad_area_nosemaphore(regs, error_code, address);
page_fault_oops(regs, error_code, address);
return;
}