From: Pierre <pinaraf@pinaraf.info>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: "open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH] Fix NULL pointer deref. on no default_rng
Date: Sat, 18 Nov 2017 18:18:19 +0100 [thread overview]
Message-ID: <1611020.Ca7VyhhiKU@peanuts2> (raw)
In-Reply-To: <CANc+2y70xppF_wZAi4urVtKGGdn4-GzVHkqEh82rxCS_pD7BDA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
On Sunday, November 12, 2017 8:16:27 PM CET PrasannaKumar Muralidharan wrote:
> Hi Pierre,
>
> On 12 November 2017 at 19:54, Pierre Ducroquet <pinaraf@pinaraf.info> wrote:
> > If crypto_get_default_rng returns an error, the
> > function ecc_gen_privkey should return an error.
> > Instead, it currently tries to use the default_rng
> > nevertheless, thus creating a kernel panic with a
> > NULL pointer dereference.
> > Returning the error directly, as was supposedly
> > intended when looking at the code, fixes this.
> >
> > Signed-off-by: Pierre Ducroquet <pinaraf@pinaraf.info>
> > ---
> >
> > crypto/ecc.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/crypto/ecc.c b/crypto/ecc.c
> > index 633a9bcdc574..18f32f2a5e1c 100644
> > --- a/crypto/ecc.c
> > +++ b/crypto/ecc.c
> > @@ -964,7 +964,7 @@ int ecc_gen_privkey(unsigned int curve_id, unsigned
> > int ndigits, u64 *privkey)>
> > * DRBG with a security strength of 256.
> > */
> >
> > if (crypto_get_default_rng())
> >
> > - err = -EFAULT;
> > + return -EFAULT;
> >
> > err = crypto_rng_get_bytes(crypto_default_rng, (u8 *)priv,
> > nbytes);
> > crypto_put_default_rng();
> >
> > --
> > 2.15.0
>
> Looks good to me.
>
> Reviewed-by: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
>
> Regards,
> PrasannaKumar
Hi
Thanks for your review.
Is there anything I should do to have this merged ? It fixes a kernel panic at
boot on my computer, so I suppose other people may have that too.
Regards
Pierre
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-18 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 14:24 [PATCH] Fix NULL pointer deref. on no default_rng Pierre Ducroquet
2017-11-12 14:46 ` PrasannaKumar Muralidharan
2017-11-18 17:18 ` Pierre [this message]
2017-11-29 6:34 ` Herbert Xu
2017-12-07 10:32 ` Pierre
2017-12-20 19:49 ` Pierre
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=1611020.Ca7VyhhiKU@peanuts2 \
--to=pinaraf@pinaraf.info \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=prasannatsmkumar@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.