mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Ying Hsu <yinghsu@chromium.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
	linux-kernel@vger.kernel.org,
	chromeos-bluetooth-upstreaming@chromium.org
Subject: Re: [PATCH] Bluetooth: Avoid potential use-after-free in hci_error_reset
Date: Thu, 04 Jan 2024 22:20:26 +0000	[thread overview]
Message-ID: <170440682632.8457.15681827016026801324.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240104115453.1.Iaa08c695d3dcf819910ea723c3eb502935638172@changeid>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Thu,  4 Jan 2024 11:56:32 +0000 you wrote:
> While handling the HCI_EV_HARDWARE_ERROR event, if the underlying
> BT controller is not responding, the GPIO reset mechanism would
> free the hci_dev and lead to a use-after-free in hci_error_reset.
> 
> Here's the call trace observed on a ChromeOS device with Intel AX201:
>    queue_work_on+0x3e/0x6c
>    __hci_cmd_sync_sk+0x2ee/0x4c0 [bluetooth <HASH:3b4a6>]
>    ? init_wait_entry+0x31/0x31
>    __hci_cmd_sync+0x16/0x20 [bluetooth <HASH:3b4a 6>]
>    hci_error_reset+0x4f/0xa4 [bluetooth <HASH:3b4a 6>]
>    process_one_work+0x1d8/0x33f
>    worker_thread+0x21b/0x373
>    kthread+0x13a/0x152
>    ? pr_cont_work+0x54/0x54
>    ? kthread_blkcg+0x31/0x31
>     ret_from_fork+0x1f/0x30
> 
> [...]

Here is the summary with links:
  - Bluetooth: Avoid potential use-after-free in hci_error_reset
    https://git.kernel.org/bluetooth/bluetooth-next/c/c6d011a4e7d3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  reply	other threads:[~2024-01-04 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 11:56 Ying Hsu
2024-01-04 22:20 ` patchwork-bot+bluetooth [this message]
2024-01-05  7:14 ` Christophe JAILLET
2024-01-05 15:36   ` Luiz Augusto von Dentz
2024-01-05 15:40     ` Luiz Augusto von Dentz

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=170440682632.8457.15681827016026801324.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=yinghsu@chromium.org \
    /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®