public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Manish Mandlik <mmandlik@google.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	chromeos-bluetooth-upstreaming@chromium.org,
	linux-bluetooth@vger.kernel.org, johan.hedberg@gmail.com,
	mcchou@google.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor()
Date: Mon, 07 Aug 2023 22:50:22 +0000	[thread overview]
Message-ID: <169144862221.1999.14693714879405886120.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230804111444.1.I43aa4bd799a3cf9102f9de8c365ccb3d8e53a9d1@changeid>

Hello:

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

On Fri,  4 Aug 2023 11:14:45 -0700 you wrote:
> KSAN reports use-after-free in hci_add_adv_monitor().
> 
> While adding an adv monitor,
>     hci_add_adv_monitor() calls ->
>     msft_add_monitor_pattern() calls ->
>     msft_add_monitor_sync() calls ->
>     msft_le_monitor_advertisement_cb() calls in an error case ->
>     hci_free_adv_monitor() which frees the *moniter.
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor()
    https://git.kernel.org/bluetooth/bluetooth-next/c/34d241ece878

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



      reply	other threads:[~2023-08-07 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 18:14 [PATCH] Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_add_adv_monitor() Manish Mandlik
2023-08-07 22:50 ` patchwork-bot+bluetooth [this message]

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=169144862221.1999.14693714879405886120.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=mcchou@google.com \
    --cc=mmandlik@google.com \
    /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