From: Pavel Begunkov <[email protected]>
To: Jordy Zomer <[email protected]>, [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH] Fix use-after-free in io_wqe_inc_running() due to wq already being free'd
Date: Mon, 15 Mar 2021 17:58:52 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 15/03/2021 17:44, Jordy Zomer wrote:
> My syzkaller instance reported a use-after-free bug in io_wqe_inc_running.
> I tried fixing this by checking if wq isn't NULL in io_wqe_worker.
> If it does; return an -EFAULT. This because create_io_worker() will clean-up the worker if there's an error.
>
> If you want I could send you the syzkaller reproducer and crash-logs :)
Yes, please.
Haven't looked up properly, but looks that wq==NULL should
never happen, so the fix is a bit racy.
>
> Best Regards,
>
> Jordy Zomer
>
> Signed-off-by: Jordy Zomer <[email protected]>
> ---
> fs/io-wq.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/fs/io-wq.c b/fs/io-wq.c
> index 0ae9ecadf295..9ed92d88a088 100644
> --- a/fs/io-wq.c
> +++ b/fs/io-wq.c
> @@ -482,6 +482,10 @@ static int io_wqe_worker(void *data)
> char buf[TASK_COMM_LEN];
>
> worker->flags |= (IO_WORKER_F_UP | IO_WORKER_F_RUNNING);
> +
> + if (wq == NULL)
> + return -EFAULT;
> +
> io_wqe_inc_running(worker);
>
> sprintf(buf, "iou-wrk-%d", wq->task_pid);
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-03-15 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 17:44 [PATCH] Fix use-after-free in io_wqe_inc_running() due to wq already being free'd Jordy Zomer
2021-03-15 17:58 ` Pavel Begunkov [this message]
2021-03-15 18:08 ` Jordy Zomer
2021-03-16 12:11 ` Pavel Begunkov
2021-03-16 14:08 ` Jordy Zomer
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