Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-usb@vger.kernel.org,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Paulian Bogdan Marinca <paulian@marinca.net>,
	Andreas Noever <andreas.noever@gmail.com>,
	Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH] thunderbolt: Fix use-after-free in remove_unplugged_switch()
Date: Wed, 18 Nov 2020 14:47:27 +0100	[thread overview]
Message-ID: <X7Ul792kd0wiXCxM@kroah.com> (raw)
In-Reply-To: <20201118133745.65628-1-mika.westerberg@linux.intel.com>

On Wed, Nov 18, 2020 at 04:37:45PM +0300, Mika Westerberg wrote:
> Paulian reported a crash that happens when a dock is unplugged during
> hibernation:
> 
> [78436.228217] thunderbolt 0-1: device disconnected
> [78436.228365] BUG: kernel NULL pointer dereference, address: 00000000000001e0
> ...
> [78436.228397] RIP: 0010:icm_free_unplugged_children+0x109/0x1a0
> ...
> [78436.228432] Call Trace:
> [78436.228439]  icm_rescan_work+0x24/0x30
> [78436.228444]  process_one_work+0x1a3/0x3a0
> [78436.228449]  worker_thread+0x30/0x370
> [78436.228454]  ? process_one_work+0x3a0/0x3a0
> [78436.228457]  kthread+0x13d/0x160
> [78436.228461]  ? kthread_park+0x90/0x90
> [78436.228465]  ret_from_fork+0x1f/0x30
> 
> This happens because remove_unplugged_switch() calls tb_switch_remove()
> that releases the memory pointed by sw so the following lines reference
> to a memory that might be released already.
> 
> Fix this by saving pointer to the parent device before calling
> tb_switch_remove().
> 
> Reported-by: Paulian Bogdan Marinca <paulian@marinca.net>
> Fixes: 4f7c2e0d8765 ("thunderbolt: Make sure device runtime resume completes before taking domain lock")
> Cc: stable@vger.kernel.org
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
>  drivers/thunderbolt/icm.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/thunderbolt/icm.c b/drivers/thunderbolt/icm.c
> index b51fc3f62b1f..05323c442b56 100644
> --- a/drivers/thunderbolt/icm.c
> +++ b/drivers/thunderbolt/icm.c
> @@ -1976,7 +1976,9 @@ static int complete_rpm(struct device *dev, void *data)
>  
>  static void remove_unplugged_switch(struct tb_switch *sw)
>  {
> -	pm_runtime_get_sync(sw->dev.parent);
> +	struct device *parent = sw->dev.parent;
> +
> +	pm_runtime_get_sync(parent);

If you are saving a pointer to a structure, shouldn't you increment the
reference count?

	struct device *parent = get_device(sw->dev.parent);

Then you know it is valid when you use it later on.

Just remember to call put_device() when you are done.

thanks,

greg k-h

  reply	other threads:[~2020-11-18 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 13:37 [PATCH] thunderbolt: Fix use-after-free in remove_unplugged_switch() Mika Westerberg
2020-11-18 13:47 ` Greg KH [this message]
2020-11-18 13:55   ` Mika Westerberg

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=X7Ul792kd0wiXCxM@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=paulian@marinca.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