From: Jens Axboe <[email protected]>
To: xiao lin <[email protected]>
Cc: Pavel Begunkov <[email protected]>,
"[email protected]" <[email protected]>,
io-uring <[email protected]>
Subject: Re: [PATCH] fs/io_uring.c: fix null ptr deference in io_send_recvmsg()
Date: Tue, 4 Aug 2020 11:15:17 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAGAoTxzadSphnE2aLsFKS04TjTKYVq2uLFgH9dvLPwWiyqEGEQ@mail.gmail.com>
On 8/4/20 11:02 AM, xiao lin wrote:
> 在 2020年8月4日星期二,Jens Axboe <[email protected] <mailto:[email protected]>> 写道:
>
> On 8/4/20 7:18 AM, Pavel Begunkov wrote:
> > On 04/08/2020 15:56, Liu Yong wrote:
> >> In io_send_recvmsg(), there is no check for the req->file.
> >> User can change the opcode from IORING_OP_NOP to IORING_OP_SENDMSG
> >> through competition after the io_req_set_file().
> >
> > After sqe->opcode is read and copied in io_init_req(), it only uses
> > in-kernel req->opcode. Also, io_init_req() should check for req->file
> > NULL, so shouldn't happen after.
> >
> > Do you have a reproducer? What kernel version did you use?
>
> Was looking at this too, and I'm guessing this is some 5.4 based kernel.
> Unfortunately the oops doesn't include that information.
> Sorry, I forgot to mention that the kernel version I am using is 5.4.55.
I think there are two options here:
1) Backport the series that ensured we only read those important bits once
2) Make s->sqe a full sqe, and memcpy it in
--
Jens Axboe
next prev parent reply other threads:[~2020-08-04 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200804125637.GA22088@ubuntu>
2020-08-04 13:18 ` [PATCH] fs/io_uring.c: fix null ptr deference in io_send_recvmsg() Pavel Begunkov
2020-08-04 13:27 ` Jens Axboe
[not found] ` <CAGAoTxzadSphnE2aLsFKS04TjTKYVq2uLFgH9dvLPwWiyqEGEQ@mail.gmail.com>
2020-08-04 17:15 ` Jens Axboe [this message]
2020-08-04 21:55 ` Jens Axboe
2020-08-05 3:40 ` Liu Yong
2020-08-05 4:10 ` 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 \
[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