summaryrefslogtreecommitdiff
path: root/crypto/sha512_generic.c
diff options
context:
space:
mode:
authorRabin Vincent <rabin.vincent@axis.com>2014-12-19 13:36:08 +0100
committerHerbert Xu <herbert@gondor.apana.org.au>2014-12-22 22:53:55 +1100
commita07663865e80890acde07f1ecc0ea2be0becbc5d (patch)
treeead0a97deaa7c777b69f2f29422597cd4a0dc668 /crypto/sha512_generic.c
parentad8b05dfadb938841880a3c05fd76e51af30b1f1 (diff)
downloadlinux-crypto-a07663865e80890acde07f1ecc0ea2be0becbc5d.tar.gz
linux-crypto-a07663865e80890acde07f1ecc0ea2be0becbc5d.zip
crypto: af_alg - fix backlog handling
If a request is backlogged, it's complete() handler will get called twice: once with -EINPROGRESS, and once with the final error code. af_alg's complete handler, unlike other users, does not handle the -EINPROGRESS but instead always completes the completion that recvmsg() is waiting on. This can lead to a return to user space while the request is still pending in the driver. If userspace closes the sockets before the requests are handled by the driver, this will lead to use-after-frees (and potential crashes) in the kernel due to the tfm having been freed. The crashes can be easily reproduced (for example) by reducing the max queue length in cryptod.c and running the following (from http://www.chronox.de/libkcapi.html) on AES-NI capable hardware: $ while true; do kcapi -x 1 -e -c '__ecb-aes-aesni' \ -k 00000000000000000000000000000000 \ -p 00000000000000000000000000000000 >/dev/null & done Cc: stable@vger.kernel.org Signed-off-by: Rabin Vincent <rabin.vincent@axis.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/sha512_generic.c')
0 files changed, 0 insertions, 0 deletions