From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [v2 PATCH 1/3] crypto: shash - Add init_tfm/exit_tfm and verify descsize
Date: Tue, 10 Dec 2019 19:30:00 -0800 [thread overview]
Message-ID: <20191211033000.GD732@sol.localdomain> (raw)
In-Reply-To: <E1idpLH-0008RO-Hn@gondobar>
On Sun, Dec 08, 2019 at 01:42:51PM +0800, Herbert Xu wrote:
> The shash interface supports a dynamic descsize field because of
> the presence of fallbacks (it's just padlock-sha actually, perhaps
> we can remove it one day). As it is the API does not verify the
> setting of descsize at all. It is up to the individual algorithms
> to ensure that descsize does not exceed the specified maximum value
> of HASH_MAX_DESCSIZE (going above would cause stack corruption).
>
> In order to allow the API to impose this limit directly, this patch
> adds init_tfm/exit_tfm hooks to the shash_alg structure. We can
> then verify the descsize setting in the API directly.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> ---
>
> crypto/shash.c | 25 +++++++++++++++++++++++++
> include/crypto/hash.h | 13 +++++++++++++
> 2 files changed, 38 insertions(+)
>
> diff --git a/crypto/shash.c b/crypto/shash.c
> index e83c5124f6eb..63a7ea368eb1 100644
> --- a/crypto/shash.c
> +++ b/crypto/shash.c
> @@ -386,15 +386,40 @@ int crypto_init_shash_ops_async(struct crypto_tfm *tfm)
> return 0;
> }
>
> +static void crypto_shash_exit_tfm(struct crypto_tfm *tfm)
> +{
> + struct crypto_shash *hash = __crypto_shash_cast(tfm);
> + struct shash_alg *alg = crypto_shash_alg(hash);
> +
> + alg->exit_tfm(hash);
> +}
> +
> static int crypto_shash_init_tfm(struct crypto_tfm *tfm)
> {
> struct crypto_shash *hash = __crypto_shash_cast(tfm);
> struct shash_alg *alg = crypto_shash_alg(hash);
> + int err;
>
> hash->descsize = alg->descsize;
>
> shash_set_needkey(hash, alg);
>
> + if (alg->exit_tfm)
> + tfm->exit = crypto_shash_exit_tfm;
> +
> + if (!alg->init_tfm)
> + return 0;
> +
> + err = alg->init_tfm(hash);
> + if (err)
> + return err;
> +
> + if (WARN_ON_ONCE(hash->descsize > HASH_MAX_DESCSIZE)) {
> + if (alg->exit_tfm)
> + alg->exit_tfm(hash);
> + return -EINVAL;
> + }
Nit: it would be helpful to have a comment just above the WARN_ON_ONCE() like:
/* ->init_tfm() may have increased the descsize. */
- Eric
next prev parent reply other threads:[~2019-12-11 3:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 2:35 [PATCH 0/3] crypto: shash - Enforce descsize limit in init_tfm Herbert Xu
2019-12-06 2:36 ` [PATCH 1/3] crypto: shash - Add init_tfm/exit_tfm and verify descsize Herbert Xu
2019-12-06 21:54 ` Eric Biggers
2019-12-06 2:36 ` [PATCH 2/3] crypto: padlock-sha - Use init_tfm/exit_tfm interface Herbert Xu
2019-12-06 2:36 ` [PATCH 3/3] crypto: hmac " Herbert Xu
2019-12-06 21:58 ` Eric Biggers
2019-12-08 5:42 ` [v2 PATCH 0/3] crypto: shash - Enforce descsize limit in init_tfm Herbert Xu
2019-12-08 5:42 ` [v2 PATCH 1/3] crypto: shash - Add init_tfm/exit_tfm and verify descsize Herbert Xu
2019-12-11 3:30 ` Eric Biggers [this message]
2019-12-08 5:42 ` [v2 PATCH 2/3] crypto: padlock-sha - Use init_tfm/exit_tfm interface Herbert Xu
2019-12-11 3:31 ` Eric Biggers
2019-12-08 5:42 ` [v2 PATCH 3/3] crypto: hmac " Herbert Xu
2019-12-11 3:32 ` [v2 PATCH 0/3] crypto: shash - Enforce descsize limit in init_tfm Eric Biggers
2019-12-11 8:30 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191211033000.GD732@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).