From: Christoph Hellwig <hch@infradead.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Hannes Reinecke <hare@suse.de>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/2] nvme-auth: Fix off by one checks
Date: Thu, 21 Jul 2022 21:48:47 -0700 [thread overview]
Message-ID: <YtosL0gGow56siA5@infradead.org> (raw)
In-Reply-To: <YtU/bFMYRCrx6tgp@kili>
Hannes, can you review these please?
On Mon, Jul 18, 2022 at 02:09:32PM +0300, Dan Carpenter wrote:
> The > ARRAY_SIZE() checks need to be >= ARRAY_SIZE() to prevent reading
> one element beyond the end of the arrays.
>
> Fixes: a476416bb57b ("nvme: implement In-Band authentication")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> The MAINTAINERS file needs to be updated for this new code.
>
> drivers/nvme/common/auth.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/nvme/common/auth.c b/drivers/nvme/common/auth.c
> index 0c86ebce59d2..bfb16fec0aed 100644
> --- a/drivers/nvme/common/auth.c
> +++ b/drivers/nvme/common/auth.c
> @@ -55,7 +55,7 @@ static struct nvme_auth_dhgroup_map {
>
> const char *nvme_auth_dhgroup_name(u8 dhgroup_id)
> {
> - if ((dhgroup_id > ARRAY_SIZE(dhgroup_map)) ||
> + if ((dhgroup_id >= ARRAY_SIZE(dhgroup_map)) ||
> !dhgroup_map[dhgroup_id].name ||
> !strlen(dhgroup_map[dhgroup_id].name))
> return NULL;
> @@ -65,7 +65,7 @@ EXPORT_SYMBOL_GPL(nvme_auth_dhgroup_name);
>
> const char *nvme_auth_dhgroup_kpp(u8 dhgroup_id)
> {
> - if ((dhgroup_id > ARRAY_SIZE(dhgroup_map)) ||
> + if ((dhgroup_id >= ARRAY_SIZE(dhgroup_map)) ||
> !dhgroup_map[dhgroup_id].kpp ||
> !strlen(dhgroup_map[dhgroup_id].kpp))
> return NULL;
> @@ -113,7 +113,7 @@ static struct nvme_dhchap_hash_map {
>
> const char *nvme_auth_hmac_name(u8 hmac_id)
> {
> - if ((hmac_id > ARRAY_SIZE(hash_map)) ||
> + if ((hmac_id >= ARRAY_SIZE(hash_map)) ||
> !hash_map[hmac_id].hmac ||
> !strlen(hash_map[hmac_id].hmac))
> return NULL;
> @@ -123,7 +123,7 @@ EXPORT_SYMBOL_GPL(nvme_auth_hmac_name);
>
> const char *nvme_auth_digest_name(u8 hmac_id)
> {
> - if ((hmac_id > ARRAY_SIZE(hash_map)) ||
> + if ((hmac_id >= ARRAY_SIZE(hash_map)) ||
> !hash_map[hmac_id].digest ||
> !strlen(hash_map[hmac_id].digest))
> return NULL;
> @@ -148,7 +148,7 @@ EXPORT_SYMBOL_GPL(nvme_auth_hmac_id);
>
> size_t nvme_auth_hmac_hash_len(u8 hmac_id)
> {
> - if ((hmac_id > ARRAY_SIZE(hash_map)) ||
> + if ((hmac_id >= ARRAY_SIZE(hash_map)) ||
> !hash_map[hmac_id].hmac ||
> !strlen(hash_map[hmac_id].hmac))
> return 0;
> --
> 2.35.1
>
>
---end quoted text---
next prev parent reply other threads:[~2022-07-22 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 11:09 [PATCH 1/2] nvme-auth: Fix off by one checks Dan Carpenter
2022-07-18 11:10 ` [PATCH] nvme-auth: Uninitialized variable in nvme_auth_transform_key() Dan Carpenter
2022-07-18 11:13 ` Dan Carpenter
2022-07-22 6:23 ` Hannes Reinecke
2022-07-22 4:48 ` Christoph Hellwig [this message]
2022-07-22 6:22 ` [PATCH 1/2] nvme-auth: Fix off by one checks Hannes Reinecke
2022-07-25 5:37 ` Christoph Hellwig
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=YtosL0gGow56siA5@infradead.org \
--to=hch@infradead.org \
--cc=dan.carpenter@oracle.com \
--cc=hare@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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