Linux-Bluetooth Archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Sungwoo Kim <iam@sung-woo.kim>
Cc: daveti@purdue.edu, benquike@gmail.com, marcel@holtmann.org,
	johan.hedberg@gmail.com, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] Bluetooth: msft: fix slab-use-after-free in msft_do_close()
Date: Wed, 01 May 2024 02:10:33 +0000	[thread overview]
Message-ID: <171452943322.31721.8564512267208580003.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240501014335.2329860-1-iam@sung-woo.kim>

Hello:

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

On Tue, 30 Apr 2024 21:43:36 -0400 you wrote:
> Dear Luiz, could you revert the v3 patch and apply this?
> 
> Fix the use-after-free bug in msft->data by tying the
> msft->data lifectime to hdev.
> Also, change msft_unregister() name to msft_release().
> 
> How msft is used after freed:
> 
> [...]

Here is the summary with links:
  - [v4] Bluetooth: msft: fix slab-use-after-free in msft_do_close()
    https://git.kernel.org/bluetooth/bluetooth-next/c/c2d3fedad3ad

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



      parent reply	other threads:[~2024-05-01  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01  1:43 [PATCH v4] Bluetooth: msft: fix slab-use-after-free in msft_do_close() Sungwoo Kim
2024-05-01  1:58 ` [v4] " bluez.test.bot
2024-05-01  2:10 ` 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=171452943322.31721.8564512267208580003.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=benquike@gmail.com \
    --cc=daveti@purdue.edu \
    --cc=iam@sung-woo.kim \
    --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 \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).