From: Jens Axboe <axboe@kernel.dk>
To: Liu Yong <pkfxxxing@gmail.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs/io_uring.c: Fix uninitialized variable is referenced in io_submit_sqe
Date: Thu, 13 Aug 2020 08:56:30 -0600 [thread overview]
Message-ID: <9fd08f8f-8c89-9c59-6d9e-5933ccc65967@kernel.dk> (raw)
In-Reply-To: <20200813065644.GA91891@ubuntu>
On 8/13/20 12:56 AM, Liu Yong wrote:
> the commit <a4d61e66ee4a> ("<io_uring: prevent re-read of sqe->opcode>")
> caused another vulnerability. After io_get_req(), the sqe_submit struct
> in req is not initialized, but the following code defaults that
> req->submit.opcode is available.
Thanks, I'll add this for 5.4-stable, it doesn't affect any kernels newer
than that.
--
Jens Axboe
prev parent reply other threads:[~2020-08-13 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 6:56 [PATCH] fs/io_uring.c: Fix uninitialized variable is referenced in io_submit_sqe Liu Yong
2020-08-13 14:56 ` Jens Axboe [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 \
--in-reply-to=9fd08f8f-8c89-9c59-6d9e-5933ccc65967@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pkfxxxing@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;
as well as URLs for NNTP newsgroup(s).