From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Roman Smirnov" <r.smirnov@omp.ru>,
"David Howells" <dhowells@redhat.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"Andrew Zaborowski" <andrew.zaborowski@intel.com>
Cc: <keyrings@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <lvc-project@linuxtesting.org>,
"Sergey Shtylyov" <s.shtylyov@omp.ru>
Subject: Re: [PATCH v2] KEYS: prevent NULL pointer dereference in find_asymmetric_key()
Date: Tue, 10 Sep 2024 16:38:37 +0300 [thread overview]
Message-ID: <D42N9ASJJSUD.EG094MFWZA4Q@kernel.org> (raw)
In-Reply-To: <20240910111806.65945-1-r.smirnov@omp.ru>
On Tue Sep 10, 2024 at 2:18 PM EEST, Roman Smirnov wrote:
> In find_asymmetric_key(), if all NULLs are passed in id_{0,1,2} parameters
> the kernel will first emit WARN and then have an oops because id_2 gets
> dereferenced anyway.
>
> Found by Linux Verification Center (linuxtesting.org) with Svace static
> analysis tool.
Weird, I recall that I've either sent a patch to address the same site
OR have commented a patch with similar reasoning. Well, it does not
matter, I think it this makes sense to me.
You could further add to the motivation that given the panic_on_warn
kernel command-line parameter, it is for the best limit the scope and
use of the WARN-macro.
>
> Fixes: 7d30198ee24f ("keys: X.509 public key issuer lookup without AKID")
I would still call this an improvement. It overuses warn but I don't
think this a bug.
> Suggested-by: Sergey Shtylyov <s.shtylyov@omp.ru>
> Signed-off-by: Roman Smirnov <r.smirnov@omp.ru>
> Reviewed-by: Sergey Shtylyov <s.shtylyov@omp.ru>
> ---
> crypto/asymmetric_keys/asymmetric_type.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/crypto/asymmetric_keys/asymmetric_type.c b/crypto/asymmetric_keys/asymmetric_type.c
> index a5da8ccd353e..43af5fa510c0 100644
> --- a/crypto/asymmetric_keys/asymmetric_type.c
> +++ b/crypto/asymmetric_keys/asymmetric_type.c
> @@ -60,17 +60,18 @@ struct key *find_asymmetric_key(struct key *keyring,
> char *req, *p;
> int len;
>
> - WARN_ON(!id_0 && !id_1 && !id_2);
> -
> if (id_0) {
> lookup = id_0->data;
> len = id_0->len;
> } else if (id_1) {
> lookup = id_1->data;
> len = id_1->len;
> - } else {
> + } else if (id_2) {
> lookup = id_2->data;
> len = id_2->len;
> + } else {
> + WARN_ON(1);
This is totally fine. It is an improvement to the current situation.
> + return ERR_PTR(-EINVAL);
> }
>
> /* Construct an identifier "id:<keyid>". */
Can be applied as an improvement and with the added bits about
panic_on_warn to the commit message.
BR, Jarkko
next prev parent reply other threads:[~2024-09-10 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 11:18 [PATCH v2] KEYS: prevent NULL pointer dereference in find_asymmetric_key() Roman Smirnov
2024-09-10 13:38 ` Jarkko Sakkinen [this message]
2024-09-10 17:38 ` Sergey Shtylyov
2024-09-11 13:18 ` Jarkko Sakkinen
2024-09-11 13:19 ` Jarkko Sakkinen
2024-09-11 14:45 ` Sergey Shtylyov
2024-09-12 14:12 ` Jarkko Sakkinen
2024-09-13 19:51 ` Jarkko Sakkinen
2024-09-12 13:51 ` Sergey Shtylyov
2024-09-12 14:27 ` Jarkko Sakkinen
2024-09-12 17:36 ` Sergey Shtylyov
2024-09-12 23:57 ` Jarkko Sakkinen
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=D42N9ASJJSUD.EG094MFWZA4Q@kernel.org \
--to=jarkko@kernel.org \
--cc=andrew.zaborowski@intel.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=r.smirnov@omp.ru \
--cc=s.shtylyov@omp.ru \
/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