Re: [PATCH] crypto: AES-NI: fix memory usage in GCM decryption

From: Herbert Xu
Date: Tue Mar 10 2015 - 05:46:01 EST

On Sun, Mar 08, 2015 at 07:49:58PM +0100, Stephan Mueller wrote:
> The RFC4106 GCM decryption operation tries to overwrite cryptlen memory
> in req->dst. As the destination buffer for decryption only needs to hold
> the plaintext memory but cryptlen references the input buffer holding
> (ciphertext || authentication tag), the assumption of the destination
> buffer length in RFC4106 GCM operation leads to a too large size.
> This patch simply subtracts the authentication tag size from cryptlen.
> The kernel crypto API logic requires the caller to provide the
> length of (ciphertext || authentication tag) as cryptlen for the
> AEAD decryption operation. Thus, the cipher implementation must
> caculate the size of the plaintext output itself and cannot simply use
> cryptlen.
> Note, this fixes a kernel crash that can be triggered from user space
> via AF_ALG(aead) without it (simply use the libkcapi test application
> from [1] and update it to use rfc4106-gcm-aes).
> [1]
> CC: Tadeusz Struk <tadeusz.struk@xxxxxxxxx>
> Signed-off-by: Stephan Mueller <smueller@xxxxxxxxxx>

Good catch. However, I think the same confusion exists in the
code that allocates src which may also trigger a crash. So could
you fix that as well?

Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page:
PGP Key:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at