public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: [email protected]
Cc: Jens Axboe <[email protected]>, Dylan Yudaken <[email protected]>,
	[email protected]
Subject: Re: [PATCH for-next 1/1] io_uring/net: fix UAF in io_sendrecv_fail()
Date: Fri, 23 Sep 2022 15:31:16 +0100	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <49ee34929051a668e4829b6549dcd3eba49bf95b.1663941567.git.asml.silence@gmail.com>

On 9/23/22 14:59, Pavel Begunkov wrote:
> We should not assume anything about ->free_iov just from
> REQ_F_ASYNC_DATA but rather rely on REQ_F_NEED_CLEANUP, as we may
> allocate ->async_data but failed init would leave the field in not
> consistent state. The easiest solution is to remove removing
> REQ_F_NEED_CLEANUP and so ->async_data dealloc from io_sendrecv_fail()
> and let io_send_zc_cleanup() do the job. The catch here is that we also
> need to prevent double notif flushing, just test it for NULL and zero
> where it's needed.
> 
> BUG: KASAN: use-after-free in io_sendrecv_fail+0x3b0/0x3e0 io_uring/net.c:1221
> Write of size 8 at addr ffff8880771b4080 by task syz-executor.3/30199
> 
> CPU: 1 PID: 30199 Comm: syz-executor.3 Not tainted 6.0.0-rc6-next-20220923-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022
> Call Trace:
>   <TASK>
>   __dump_stack lib/dump_stack.c:88 [inline]
>   dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
>   print_address_description mm/kasan/report.c:284 [inline]
>   print_report+0x15e/0x45d mm/kasan/report.c:395
>   kasan_report+0xbb/0x1f0 mm/kasan/report.c:495
>   io_sendrecv_fail+0x3b0/0x3e0 io_uring/net.c:1221
>   io_req_complete_failed+0x155/0x1b0 io_uring/io_uring.c:873
>   io_drain_req io_uring/io_uring.c:1648 [inline]
>   io_queue_sqe_fallback.cold+0x29f/0x788 io_uring/io_uring.c:1931
>   io_submit_sqe io_uring/io_uring.c:2160 [inline]
>   io_submit_sqes+0x1180/0x1df0 io_uring/io_uring.c:2276
>   __do_sys_io_uring_enter+0xac6/0x2410 io_uring/io_uring.c:3216
>   do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>   do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
>   entry_SYSCALL_64_after_hwframe+0x63/0xcd

Missed unused var, will resend

> 
> Fixes: c4c0009e0b56e ("io_uring/net: combine fail handlers")
> Reported-by: [email protected]
> Signed-off-by: Pavel Begunkov <[email protected]>
> ---
>   io_uring/net.c | 14 +++++---------
>   1 file changed, 5 insertions(+), 9 deletions(-)
> 
> diff --git a/io_uring/net.c b/io_uring/net.c
> index 757a300578f4..e9e66bace45f 100644
> --- a/io_uring/net.c
> +++ b/io_uring/net.c
> @@ -915,9 +915,11 @@ void io_send_zc_cleanup(struct io_kiocb *req)
>   		io = req->async_data;
>   		kfree(io->free_iov);
>   	}
> -	zc->notif->flags |= REQ_F_CQE_SKIP;
> -	io_notif_flush(zc->notif);
> -	zc->notif = NULL;
> +	if (zc->notif) {
> +		zc->notif->flags |= REQ_F_CQE_SKIP;
> +		io_notif_flush(zc->notif);
> +		zc->notif = NULL;
> +	}
>   }
>   
>   int io_send_zc_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)
> @@ -1215,12 +1217,6 @@ void io_sendrecv_fail(struct io_kiocb *req)
>   		io_notif_flush(sr->notif);
>   		sr->notif = NULL;
>   	}
> -	if (req_has_async_data(req)) {
> -		io = req->async_data;
> -		kfree(io->free_iov);
> -		io->free_iov = NULL;
> -	}
> -	req->flags &= ~REQ_F_NEED_CLEANUP;
>   	io_req_set_res(req, res, req->cqe.flags);
>   }
>   

-- 
Pavel Begunkov

      reply	other threads:[~2022-09-23 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 13:59 [PATCH for-next 1/1] io_uring/net: fix UAF in io_sendrecv_fail() Pavel Begunkov
2022-09-23 14:31 ` Pavel Begunkov [this message]

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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