From: Corey Minyard <minyard@acm.org>
To: Masamitsu Yamazaki <m-yamazaki@ah.jp.nec.com>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Junichi Nomura <j-nomura@ce.jp.nec.com>,
Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Subject: Re: [PATCH] ipmi: Clear smi_info->thread to prevent use-after-free during module unload
Date: Mon, 15 Jan 2018 18:40:24 -0600 [thread overview]
Message-ID: <e065b483-43e5-3297-0d5f-01e592a306aa@acm.org> (raw)
In-Reply-To: <20180115080427.GA29559@53Xg1.linux.bs1.fc.nec.co.jp>
On 01/15/2018 01:58 AM, Masamitsu Yamazaki wrote:
> Subject:[PATCH] ipmi: Clear smi_info->thread to prevent use-after-free during module unload
> To: Corey Minyard <minyard@acm.org>
> To: openipmi-developer@lists.sourceforge.net
> Cc: linux-kernel@vger.kernel.org
> Cc: j-nomura@ce.jp.nec.com
> Cc: k-ueda@ct.jp.nec.com
> Cc: m-yamazaki@ah.jp.nec.com
In the future, please don't include the above, and please don't use a
normal mailer to send the
email. It came MIME encoded, so it's very hard to deal with. Use "git
send-email" to send, if
at all possible.
>
> During code inspection, I found an use-after-free possibility during unloading
> ipmi_si in the polling mode.
I'm curious, what exactly is this code inspection part of? Are you
reviewing all the code
in the kernel? Are you having certain people own certain drivers?
> If start_new_msg() is called after kthread_stop(), the function will try to
> wake up non-existing kthread using the dangling pointer.
>
> Possible scenario is when a new internal message is generated after
> ipmi_unregister_smi()[*1] and remains after stop_timer_and_thread()
> in clenaup_one_si() [*2].
> Use-after-free could occur as follows depending on BMC replies.
>
> cleanup_one_si
> => ipmi_unregister_smi
> [*1]
> => stop_timer_and_thread
> => kthread_stop(smi_info->thread)
> [*2]
> => poll
> => smi_event_handler
> => start_new_msg
> => if (smi_info->thread)
> wake_up_process(smi_info->thread) <== use-after-free!!
>
> Although currently it seems no such message is generated in the polling mode,
> some changes might introduce that in thefuture. For example in the interrupt
> mode, disable_si_irq() does that at [*2].
>
> So let's prevent such a critical issue possibility now.
I don't have a problem with this, it's included for the next merge window.
Thanks,
-corey
>
> Signed-off-by: Yamazaki Masamitsu <m-yamazaki@ah.jp.nec.com>
>
>
> diff -Nurp a/drivers/char/ipmi/ipmi_si_intf.c b/drivers/char/ipmi/ipmi_si_intf.c
> --- a/drivers/char/ipmi/ipmi_si_intf.c 2018-01-09 13:40:14.624785104 +0900
> +++ b/drivers/char/ipmi/ipmi_si_intf.c 2018-01-09 13:44:39.174780570 +0900
> @@ -1938,8 +1938,10 @@ static void check_for_broken_irqs(struct
>
> static inline void stop_timer_and_thread(struct smi_info *smi_info)
> {
> - if (smi_info->thread != NULL)
> + if (smi_info->thread != NULL) {
> kthread_stop(smi_info->thread);
> + smi_info->thread = NULL;
> + }
>
> smi_info->timer_can_start = false;
> if (smi_info->timer_running)
next prev parent reply other threads:[~2018-01-16 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 7:58 Masamitsu Yamazaki
2018-01-16 0:40 ` Corey Minyard [this message]
2018-01-16 7:54 ` Masamitsu Yamazaki
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=e065b483-43e5-3297-0d5f-01e592a306aa@acm.org \
--to=minyard@acm.org \
--cc=j-nomura@ce.jp.nec.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-yamazaki@ah.jp.nec.com \
--cc=openipmi-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®