From: Ming Lei <ming.lei@redhat.com>
To: linan666@huaweicloud.com
Cc: josef@toxicpanda.com, axboe@kernel.dk,
linux-block@vger.kernel.org, nbd@other.debian.org,
linux-kernel@vger.kernel.org, linan122@huawei.com,
yukuai3@huawei.com, yi.zhang@huawei.com, houtao1@huawei.com,
yangerkun@huawei.com, ming.lei@redhat.com
Subject: Re: [PATCH] nbd: pass nbd_sock to nbd_read_reply() instead of index
Date: Thu, 28 Sep 2023 12:05:05 +0800 [thread overview]
Message-ID: <ZRT7cVFcE6QMHfie@fedora> (raw)
In-Reply-To: <20230911023308.3467802-1-linan666@huaweicloud.com>
On Mon, Sep 11, 2023 at 10:33:08AM +0800, linan666@huaweicloud.com wrote:
> From: Li Nan <linan122@huawei.com>
>
> If a socket is processing ioctl 'NBD_SET_SOCK', config->socks might be
> krealloc in nbd_add_socket(), and a garbage request is received now, a UAF
> may occurs.
>
> T1
> nbd_ioctl
> __nbd_ioctl
> nbd_add_socket
> blk_mq_freeze_queue
> T2
> recv_work
> nbd_read_reply
> sock_xmit
> krealloc config->socks
> def config->socks
>
> Pass nbd_sock to nbd_read_reply(). And introduce a new function
> sock_xmit_recv(), which differs from sock_xmit only in the way it get
> socket.
>
I am wondering why not grab queue usage counter before calling nbd_read_reply()
for avoiding such issue, something like the following change:
diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
index df1cd0f718b8..09215b605b12 100644
--- a/drivers/block/nbd.c
+++ b/drivers/block/nbd.c
@@ -837,9 +837,6 @@ static void recv_work(struct work_struct *work)
while (1) {
struct nbd_reply reply;
- if (nbd_read_reply(nbd, args->index, &reply))
- break;
-
/*
* Grab .q_usage_counter so request pool won't go away, then no
* request use-after-free is possible during nbd_handle_reply().
@@ -852,6 +849,9 @@ static void recv_work(struct work_struct *work)
break;
}
+ if (nbd_read_reply(nbd, args->index, &reply))
+ break;
+
cmd = nbd_handle_reply(nbd, args->index, &reply);
if (IS_ERR(cmd)) {
percpu_ref_put(&q->q_usage_counter);
Thanks,
Ming
next prev parent reply other threads:[~2023-09-28 4:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 2:33 [PATCH] nbd: pass nbd_sock to nbd_read_reply() instead of index linan666
2023-09-28 3:40 ` Li Nan
2023-09-28 4:05 ` Ming Lei [this message]
2023-09-28 6:03 ` Yu Kuai
2023-09-28 7:40 ` Ming Lei
2023-09-28 8:55 ` Yu Kuai
2023-09-28 8:57 ` Ming Lei
2023-09-28 9:06 ` Yu Kuai
2023-09-28 9:24 ` Ming Lei
2023-09-28 9:40 ` Yu Kuai
2023-10-30 2:07 ` Yu Kuai
2023-10-30 12:42 ` Ming Lei
2023-10-30 13:16 ` Yu Kuai
2023-11-21 6:16 ` Li Nan
2023-11-21 14:42 ` Jens Axboe
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=ZRT7cVFcE6QMHfie@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=houtao1@huawei.com \
--cc=josef@toxicpanda.com \
--cc=linan122@huawei.com \
--cc=linan666@huaweicloud.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@other.debian.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox