crypto: skcipher - Copy iv from desc even for 0-len walks
authorJason A. Donenfeld <Jason@zx2c4.com>
Sun, 6 Dec 2015 01:51:37 +0000 (02:51 +0100)
committerBen Hutchings <ben@decadent.org.uk>
Fri, 22 Jan 2016 21:40:03 +0000 (21:40 +0000)
commitf659a818a42f4be9cffdc8bda4afca8b7cc5d98d
tree0d19e526d288e81de29a0ccdb4e30f604bbfd99b
parent4942dccb5d2ca761c835dc2e07d3604f60771473
crypto: skcipher - Copy iv from desc even for 0-len walks

commit 70d906bc17500edfa9bdd8c8b7e59618c7911613 upstream.

Some ciphers actually support encrypting zero length plaintexts. For
example, many AEAD modes support this. The resulting ciphertext for
those winds up being only the authentication tag, which is a result of
the key, the iv, the additional data, and the fact that the plaintext
had zero length. The blkcipher constructors won't copy the IV to the
right place, however, when using a zero length input, resulting in
some significant problems when ciphers call their initialization
routines, only to find that the ->iv parameter is uninitialized. One
such example of this would be using chacha20poly1305 with a zero length
input, which then calls chacha20, which calls the key setup routine,
which eventually OOPSes due to the uninitialized ->iv member.

Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
crypto/ablkcipher.c
crypto/blkcipher.c