mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Jens Axboe <axboe@kernel.dk>, Hao-Yu Yang <naup96721@gmail.com>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
	 kernel-team@meta.com, Breno Leitao <leitao@debian.org>
Subject: [PATCH] io_uring/kbuf: fix use-after-free of new iovec on bundle grow
Date: Mon, 13 Jul 2026 05:51:06 -0700	[thread overview]
Message-ID: <20260713-io_uring_dangling-v1-1-b9bdc0f0e776@debian.org> (raw)

When io_ring_buffers_peek() grows a provided-buffer bundle, it allocates
a new iovec array and points arg->iovs at it. The KBUF_MODE_FREE cleanup
added at the end of the function then does kfree(arg->iovs), which frees
this freshly allocated array that is about to be returned to and used by
the caller, instead of the old cached iovec (org_iovs) it was meant to
release. The caller reads the now-freed array, resulting in a
use-after-free, easily triggered by the liburing recv-bundle-short-ooo
test:

  BUG: KASAN: slab-use-after-free in io_recv+0x4bc/0xc60
  Read of size 8 at addr ffff00037b20c240 by task recv-bundle-sho
   io_recv
  Allocated by task:
   __kmalloc_noprof
   io_ring_buffers_peek
   io_buffers_peek
   io_recv
  Freed by task:
   kfree
   io_ring_buffers_peek
   io_buffers_peek
   io_recv

Free org_iovs instead, and only when it was actually replaced by a new
allocation. On the access_ok() failure path the new array is already
freed and the request is left pointing at the original iovec, so nothing
needs to be released at this point in that case.

Fixes: cd053d788c3f ("io_uring: fix dangling iovec after provided-buffer bundle grow failure")
Signed-off-by: Breno Leitao <leitao@debian.org>
---
 io_uring/kbuf.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/io_uring/kbuf.c b/io_uring/kbuf.c
index b6b969b55e122..07d81dc7cbe29 100644
--- a/io_uring/kbuf.c
+++ b/io_uring/kbuf.c
@@ -328,8 +328,8 @@ 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 ((arg->mode & KBUF_MODE_FREE) && arg->iovs != org_iovs)
+		kfree(org_iovs);
 
 	if (head == tail)
 		req->flags |= REQ_F_BL_EMPTY;

---
base-commit: bee763d5f341b99cf472afeb508d4988f62a6ca1
change-id: 20260713-io_uring_dangling-87c23d568135

Best regards,
--  
Breno Leitao <leitao@debian.org>


             reply	other threads:[~2026-07-13 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 12:51 Breno Leitao [this message]
2026-07-14 14:01 ` Gabriel Krisman Bertazi
2026-07-14 16:00   ` Breno Leitao

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=20260713-io_uring_dangling-v1-1-b9bdc0f0e776@debian.org \
    --to=leitao@debian.org \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naup96721@gmail.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

Powered by JetHome