summaryrefslogtreecommitdiff
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorBreno Leitao <leitao@debian.org>2019-01-30 15:46:00 +0300
committerMichael Ellerman <mpe@ellerman.id.au>2019-02-06 16:29:20 +0300
commitebb0e13ead2ddc186a80b1b0235deeefc5a1a667 (patch)
treef5b2a47adf9de7f15504c5051a9e13e4d6ab51fd /MAINTAINERS
parent98ecc6768e8fdba95da1fc1efa0ef2d769e7fe1c (diff)
downloadlinux-ebb0e13ead2ddc186a80b1b0235deeefc5a1a667.tar.xz
powerpc/ptrace: Mitigate potential Spectre v1
'regno' is directly controlled by user space, hence leading to a potential exploitation of the Spectre variant 1 vulnerability. On PTRACE_SETREGS and PTRACE_GETREGS requests, user space passes the register number that would be read or written. This register number is called 'regno' which is part of the 'addr' syscall parameter. This 'regno' value is checked against the maximum pt_regs structure size, and then used to dereference it, which matches the initial part of a Spectre v1 (and Spectre v1.1) attack. The dereferenced value, then, is returned to userspace in the GETREGS case. This patch sanitizes 'regno' before using it to dereference pt_reg. Notice that given that speculation windows are large, the policy is to kill the speculation on the first load and not worry if it can be completed with a dependent load/store [1]. [1] https://marc.info/?l=linux-kernel&m=152449131114778&w=2 Signed-off-by: Breno Leitao <leitao@debian.org> Acked-by: Gustavo A. R. Silva <gustavo@embeddedor.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions