summaryrefslogtreecommitdiff
path: root/crypto/async_tx
diff options
context:
space:
mode:
authorRomain Izard <romain.izard.pro@gmail.com>2017-10-31 15:42:35 +0100
committerHerbert Xu <herbert@gondor.apana.org.au>2017-11-03 21:35:35 +0800
commitac3f51069c1b0fb5150e527605afddef129c107c (patch)
tree550bad83d718c041c0fd56799c27f35869c5758c /crypto/async_tx
parent58425dc5a756e7d9cab4d4f0632c0455e1419279 (diff)
downloadlinux-crypto-ac3f51069c1b0fb5150e527605afddef129c107c.tar.gz
linux-crypto-ac3f51069c1b0fb5150e527605afddef129c107c.zip
crypto: ccm - preserve the IV buffer
The IV buffer used during CCM operations is used twice, during both the hashing step and the ciphering step. When using a hardware accelerator that updates the contents of the IV buffer at the end of ciphering operations, the value will be modified. In the decryption case, the subsequent setup of the hashing algorithm will interpret the updated IV instead of the original value, which can lead to out-of-bounds writes. Reuse the idata buffer, only used in the hashing step, to preserve the IV's value during the ciphering step in the decryption case. Signed-off-by: Romain Izard <romain.izard.pro@gmail.com> Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com> Cc: <stable@vger.kernel.org> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/async_tx')
0 files changed, 0 insertions, 0 deletions