From: Sean Anderson <seanga2@gmail.com>
To: Bob Wolff <bob.wolff68@gmail.com>, u-boot@lists.denx.de
Cc: pbrobinson@gmail.com, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] Check curve_name for null to avoid crash
Date: Thu, 22 Feb 2024 20:24:20 -0500 [thread overview]
Message-ID: <801f58e6-2b23-8a85-b3aa-fb81f4fde2a4@gmail.com> (raw)
In-Reply-To: <20240222221814.3496-1-bob.wolff68@gmail.com>
On 2/22/24 17:18, Bob Wolff wrote:
> If mixed rsa and ecdsa keys are specified in dtsi, an rsa key can be sent
> into the ecdsa verify. Without the ecdsa,curve property, this function will
> crash due to lack of checking the null pointer return.
nit: there should be a blank line here
> Signed-off-by: Bob Wolff <bob.wolff68@gmail.com>
> ---
>
> lib/ecdsa/ecdsa-verify.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/lib/ecdsa/ecdsa-verify.c b/lib/ecdsa/ecdsa-verify.c
> index 0601700c4f..4d1835b598 100644
> --- a/lib/ecdsa/ecdsa-verify.c
> +++ b/lib/ecdsa/ecdsa-verify.c
> @@ -31,6 +31,11 @@ static int fdt_get_key(struct ecdsa_public_key *key, const void *fdt, int node)
> int x_len, y_len;
>
> key->curve_name = fdt_getprop(fdt, node, "ecdsa,curve", NULL);
> + if (!key->curve_name) {
> + debug("Error: ecdsa cannot get 'ecdsa,curve' property from key. Likely not an ecdsa key.\n");
> + return -ENOMSG;
> + }
> +
> key->size_bits = ecdsa_key_size(key->curve_name);
> if (key->size_bits == 0) {
> debug("Unknown ECDSA curve '%s'", key->curve_name);
Reviewed-by: Sean Anderson <seanga2@gmail.com>
next prev parent reply other threads:[~2024-02-23 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 22:18 [PATCH] Check curve_name for null to avoid crash Bob Wolff
2024-02-23 1:24 ` Sean Anderson [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 23:57 Bob Wolff
2024-03-06 22:55 ` Bob Wolff
2024-03-07 17:12 ` Tom Rini
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=801f58e6-2b23-8a85-b3aa-fb81f4fde2a4@gmail.com \
--to=seanga2@gmail.com \
--cc=bob.wolff68@gmail.com \
--cc=pbrobinson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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