]> git.baikalelectronics.ru Git - kernel.git/commit
ipmi: Clear smi_info->thread to prevent use-after-free during module unload
authorMasamitsu Yamazaki <m-yamazaki@ah.jp.nec.com>
Mon, 15 Jan 2018 07:58:12 +0000 (07:58 +0000)
committerCorey Minyard <cminyard@mvista.com>
Tue, 16 Jan 2018 00:34:34 +0000 (18:34 -0600)
commitbd1c06a4f5e2b2c96b9ff09a13983efb2d013b18
treee16878d2f5d00327bad77ef2b19325d53aeac386
parent1b4254cee0643ae624d33481b5107b790ae581b9
ipmi: Clear smi_info->thread to prevent use-after-free during module unload

During code inspection, I found an use-after-free possibility during unloading
ipmi_si in the polling mode.

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.

Signed-off-by: Yamazaki Masamitsu <m-yamazaki@ah.jp.nec.com>
Signed-off-by: Corey Minyard <cminyard@mvista.com>
drivers/char/ipmi/ipmi_si_intf.c