summaryrefslogtreecommitdiff
path: root/virt/kvm
diff options
context:
space:
mode:
authorKees Cook <keescook@chromium.org>2017-04-05 16:39:08 (GMT)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-04-21 07:31:24 (GMT)
commit2c0ad235ac77f2fc2eee593bf06822cad772e0e2 (patch)
tree0ca5b8a057ee9182efe7c0a50524bdba24751645 /virt/kvm
parentef793e6e113473f7cb08edf1ca4a8737c57ce51c (diff)
downloadlinux-2c0ad235ac77f2fc2eee593bf06822cad772e0e2.tar.xz
mm: Tighten x86 /dev/mem with zeroing reads
commit a4866aa812518ed1a37d8ea0c881dc946409de94 upstream. Under CONFIG_STRICT_DEVMEM, reading System RAM through /dev/mem is disallowed. However, on x86, the first 1MB was always allowed for BIOS and similar things, regardless of it actually being System RAM. It was possible for heap to end up getting allocated in low 1MB RAM, and then read by things like x86info or dd, which would trip hardened usercopy: usercopy: kernel memory exposure attempt detected from ffff880000090000 (dma-kmalloc-256) (4096 bytes) This changes the x86 exception for the low 1MB by reading back zeros for System RAM areas instead of blindly allowing them. More work is needed to extend this to mmap, but currently mmap doesn't go through usercopy, so hardened usercopy won't Oops the kernel. Reported-by: Tommi Rantala <tommi.t.rantala@nokia.com> Tested-by: Tommi Rantala <tommi.t.rantala@nokia.com> Signed-off-by: Kees Cook <keescook@chromium.org> Cc: Brad Spengler <spender@grsecurity.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions