summaryrefslogtreecommitdiffstats
path: root/virt/kvm
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2019-04-09 23:46:31 -0700
committerHerbert Xu <herbert@gondor.apana.org.au>2019-04-18 22:14:58 +0800
commit767f015ea0b7ab9d60432ff6cd06b664fd71f50f (patch)
tree92dc0f57cf5a5662f25a33a73f8a2af24d74bfd5 /virt/kvm
parentedaf28e996af69222b2cb40455dbb5459c2b875a (diff)
downloadlinux-stable-767f015ea0b7ab9d60432ff6cd06b664fd71f50f.tar.gz
linux-stable-767f015ea0b7ab9d60432ff6cd06b664fd71f50f.tar.bz2
linux-stable-767f015ea0b7ab9d60432ff6cd06b664fd71f50f.zip
crypto: arm/aes-neonbs - don't access already-freed walk.iv
If the user-provided IV needs to be aligned to the algorithm's alignmask, then skcipher_walk_virt() copies the IV into a new aligned buffer walk.iv. But skcipher_walk_virt() can fail afterwards, and then if the caller unconditionally accesses walk.iv, it's a use-after-free. arm32 xts-aes-neonbs doesn't set an alignmask, so currently it isn't affected by this despite unconditionally accessing walk.iv. However this is more subtle than desired, and it was actually broken prior to the alignmask being removed by commit cc477bf64573 ("crypto: arm/aes - replace bit-sliced OpenSSL NEON code"). Thus, update xts-aes-neonbs to start checking the return value of skcipher_walk_virt(). Fixes: e4e7f10bfc40 ("ARM: add support for bit sliced AES using NEON instructions") Cc: <stable@vger.kernel.org> # v3.13+ Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'virt/kvm')
0 files changed, 0 insertions, 0 deletions