From: Hao-Yu Yang <naup96721@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: axboe@kernel.dk, io-uring@vger.kernel.org
Subject: Re: [PATCH v2] io_uring: fix dangling iovec after provided-buffer bundle grow failure
Date: Tue, 7 Jul 2026 03:01:23 +0800 [thread overview]
Message-ID: <akv7g/e+0wzWpZkE@naup-virtual-machine> (raw)
In-Reply-To: <20260706183304.919275-1-naup96721@gmail.com>
On Tue, Jul 07, 2026 at 02:33:04AM +0800, Hao-Yu Yang wrote:
> When growing a provided-buffer bundle, the old cached iovec is freed
> before the new buffers have all been validated. If validation fails, the
> request still points at the freed iovec, which can be freed again during
> completion cleanup.
>
> BUG: KASAN: double-free in io_vec_free+0x2c/0x90
> Freed by task 73:
> kfree+0x104/0x3b0
> io_vec_free+0x2c/0x90
> __io_submit_flush_completions+0xc03/0x1e40
> io_submit_sqes+0xdb5/0x2310
>
> Allocated by task 73:
> io_ring_buffers_peek+0x559/0xc60
> io_buffers_select+0x1c1/0x460
> io_send+0x770/0x1050
>
> Fix this by deferring the free of the old cached iovec until validation
> has succeeded. On failure, free the newly allocated iovec and leave the
> request pointing at the original one.
>
> change log:
> v2: slimming v1 patch
>
> Fixes: 46800585ae04 ("io_uring/kbuf: validate ring provided buffer addresses with access_ok()")
> Signed-off-by: Hao-Yu Yang <naup96721@gmail.com>
> ---
> io_uring/kbuf.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
> index 3cd29477fff2..b6b969b55e12 100644
> --- a/io_uring/kbuf.c
> +++ b/io_uring/kbuf.c
> @@ -287,8 +287,6 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
> iov = kmalloc_objs(struct iovec, nr_avail);
> if (unlikely(!iov))
> return -ENOMEM;
> - if (arg->mode & KBUF_MODE_FREE)
> - kfree(arg->iovs);
> arg->iovs = iov;
> nr_iovs = nr_avail;
> } else if (nr_avail < nr_iovs) {
> @@ -330,6 +328,9 @@ static int io_ring_buffers_peek(struct io_kiocb *req, struct buf_sel_arg *arg,
> buf = io_ring_head_to_buf(br, ++head, bl->mask);
> } while (--nr_iovs);
>
> + if (arg->mode & KBUF_MODE_FREE)
> + kfree(arg->iovs);
> +
> if (head == tail)
> req->flags |= REQ_F_BL_EMPTY;
>
> --
> 2.34.1
>
Just sent this v2 patch and wait for this patch merge? I need to do anything else?
next prev parent reply other threads:[~2026-07-06 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 18:33 Hao-Yu Yang
2026-07-06 19:01 ` Hao-Yu Yang [this message]
2026-07-07 0:50 ` 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=akv7g/e+0wzWpZkE@naup-virtual-machine \
--to=naup96721@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®