summaryrefslogtreecommitdiff
path: root/net/dccp
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavo@embeddedor.com>2018-06-29 21:28:07 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-07-22 15:25:52 +0300
commitaf4bae09386c787fbc2fa9b69a50d65eba4b6e30 (patch)
tree6af40244d3cbf61b1c812565eefc936d7dbbeb0d /net/dccp
parent517340a7ef476a44905fdb001c4a3dd824d99c3b (diff)
downloadlinux-af4bae09386c787fbc2fa9b69a50d65eba4b6e30.tar.xz
atm: zatm: Fix potential Spectre v1
[ Upstream commit ced9e191501e52b95e1b57b8e0db00943869eed0 ] pool can be indirectly controlled by user-space, hence leading to a potential exploitation of the Spectre variant 1 vulnerability. This issue was detected with the help of Smatch: drivers/atm/zatm.c:1491 zatm_ioctl() warn: potential spectre issue 'zatm_dev->pool_info' (local cap) Fix this by sanitizing pool before using it to index zatm_dev->pool_info 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: Gustavo A. R. Silva <gustavo@embeddedor.com> Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/dccp')
0 files changed, 0 insertions, 0 deletions