> Validate that the provided rte_crypto_auth_xform's key length is not
> too large, and that the provided data pointer is not NULL.
>
> Previously, providing a key which has a size > SHA_BLOCK_MAX will cause
> the key memcpy to write out of bounds. Since the rte_crypto_auth_xform
> documentation states that it is the user's responsibility to validate
> the authentication key length, this is not a bug in DPDK. However,
> other PMDs are validating this, and it is more user-friendly to do so -
> with negligible performance impact.
>
> Reported-by: pengpeng <[email protected]>
> Signed-off-by: Jack Bond-Preston <[email protected]>
> Reviewed-by: Wathsala Vithanage <[email protected]>
> ---
Applied to dpdk-next-crypto
Fixes: 169ca3db550c ("crypto/armv8: add PMD optimized for ARMv8 processors")
Cc: [email protected]