From: Hannes Reinecke <hare@suse.de>
To: Weiming Shi <bestswngs@gmail.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
co+77553a7fc66ac133@bugs.sh, Xiang Mei <xmei5@asu.edu>,
stable@vger.kernel.org
Subject: Re: [PATCH] nvmet-auth: fix out-of-bounds write in nvmet_auth_challenge()
Date: Fri, 18 Sep 2026 17:17:18 +0200 [thread overview]
Message-ID: <46322855-6496-482c-a63b-d0e7bd055f1b@suse.de> (raw)
In-Reply-To: <20260912171009.1513289-3-bestswngs@gmail.com>
On 9/12/26 7:10 PM, Weiming Shi wrote:
> nvmet_auth_challenge() receives its output buffer as a void pointer.
> sizeof(*d) therefore evaluates to one with GCC and undercounts the fixed
> challenge header by 15 bytes. A short AUTH_RECEIVE buffer can pass the
> check before the challenge is copied past the end of its allocation.
>
> Use the typed challenge pointer when calculating the response size.
>
> BUG: KASAN: slab-out-of-bounds in nvmet_execute_auth_receive (drivers/nvme/target/fabrics-cmd-auth.c:442 drivers/nvme/target/fabrics-cmd-auth.c:569)
> Write of size 32 by task kworker/1:1H/64
> Workqueue: nvmet_tcp_wq nvmet_tcp_io_work
> Call Trace:
> nvmet_execute_auth_receive (drivers/nvme/target/fabrics-cmd-auth.c:442 drivers/nvme/target/fabrics-cmd-auth.c:569)
> nvmet_tcp_try_recv_pdu (drivers/nvme/target/tcp.c:1119 drivers/nvme/target/tcp.c:1243)
> nvmet_tcp_io_work (drivers/nvme/target/tcp.c:1350 drivers/nvme/target/tcp.c:1382 drivers/nvme/target/tcp.c:1445)
> process_one_work (kernel/workqueue.c:3322)
> worker_thread (kernel/workqueue.c:3405 kernel/workqueue.c:3486)
> kthread (kernel/kthread.c:436)
> ret_from_fork (arch/x86/kernel/process.c:158)
> ret_from_fork_asm (arch/x86/entry/entry_64.S:245)
> The buggy address is located 16 bytes inside of
> allocated 33-byte region [ffff888000554e80, ffff888000554ea1)
> Kernel panic - not syncing: KASAN: panic_on_warn set ...
>
> Cc: stable@vger.kernel.org
> Fixes: db1312dd9548 ("nvmet: implement basic In-Band Authentication")
> Reported-by: co+77553a7fc66ac133@bugs.sh
> Closes: https://lore.kernel.org/all/Ah6QavQXwvshtqyUcYD1P1R7XE0ND9fB7lbV@bugs.sh/
> Assisted-by: Codex:gpt-5.6
> Signed-off-by: Weiming Shi <bestswngs@gmail.com>
> ---
> drivers/nvme/target/fabrics-cmd-auth.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/target/fabrics-cmd-auth.c b/drivers/nvme/target/fabrics-cmd-auth.c
> index 92f8a76f10..dccdb55a36 100644
> --- a/drivers/nvme/target/fabrics-cmd-auth.c
> +++ b/drivers/nvme/target/fabrics-cmd-auth.c
> @@ -427,7 +427,7 @@ static int nvmet_auth_challenge(struct nvmet_req *req, void *d, int al)
> struct nvmet_ctrl *ctrl = req->sq->ctrl;
> int ret = 0;
> int hash_len = nvme_auth_hmac_hash_len(ctrl->shash_id);
> - int data_size = sizeof(*d) + hash_len;
> + int data_size = sizeof(*data) + hash_len;
>
> if (ctrl->dh_tfm)
> data_size += ctrl->dh_keysize;
Reviewed-by: Hannes Reinecke <hare@kernel.org>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-09-18 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 17:10 Weiming Shi
2026-09-18 12:31 ` Christoph Hellwig
2026-09-18 15:17 ` Hannes Reinecke [this message]
2026-09-18 15:18 ` Keith Busch
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=46322855-6496-482c-a63b-d0e7bd055f1b@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=bestswngs@gmail.com \
--cc=co+77553a7fc66ac133@bugs.sh \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=stable@vger.kernel.org \
--cc=xmei5@asu.edu \
/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
all inboxes | Powered by JetHome®