Revision 7a7003b1da010d2b0d1dc8bf21c10f5c73b389f1 authored by Mark Rutland on 02 November 2017, 16:12:03 UTC, committed by Catalin Marinas on 02 November 2017, 18:33:08 UTC
It's possible for a user to deliberately trigger __dump_instr with a
chosen kernel address.
Let's avoid problems resulting from this by using get_user() rather than
__get_user(), ensuring that we don't erroneously access kernel memory.
Where we use __dump_instr() on kernel text, we already switch to
KERNEL_DS, so this shouldn't adversely affect those cases.
Fixes: 60ffc30d5652810d ("arm64: Exception handling")
Cc: stable@vger.kernel.org
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
1 parent 0b07194
| File | Mode | Size |
|---|---|---|
| .gitignore | -rw-r--r-- | 29 bytes |
| Makefile | -rw-r--r-- | 1.4 KB |
| bpf-direct.c | -rw-r--r-- | 4.9 KB |
| bpf-fancy.c | -rw-r--r-- | 2.4 KB |
| bpf-helper.c | -rw-r--r-- | 2.4 KB |
| bpf-helper.h | -rw-r--r-- | 7.3 KB |
| dropper.c | -rw-r--r-- | 1.9 KB |
Computing file changes ...
