All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Edward Adam Davis <eadavis@qq.com>
Cc: syzbot+9aa47cd4633a3cf92a80@syzkaller.appspotmail.com,
	johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, luiz.dentz@gmail.com,
	marcel@holtmann.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] Bluetooth: hci_sock: Prevent race in socket write iter and sock bind
Date: Wed, 19 Nov 2025 14:30:07 +0000	[thread overview]
Message-ID: <176356260726.811862.764219010634757763.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_279508EB2AECDECC2C79466F582D896E980A@qq.com>

Hello:

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

On Sun, 16 Nov 2025 17:04:43 +0800 you wrote:
> There is a potential race condition between sock bind and socket write
> iter. bind may free the same cmd via mgmt_pending before write iter sends
> the cmd, just as syzbot reported in UAF[1].
> 
> Here we use hci_dev_lock to synchronize the two, thereby avoiding the
> UAF mentioned in [1].
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_sock: Prevent race in socket write iter and sock bind
    https://git.kernel.org/bluetooth/bluetooth-next/c/1f738d68430c

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



      parent reply	other threads:[~2025-11-19 14:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16  6:34 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in mgmt_pending_remove syzbot
2025-11-16  8:02 ` Edward Adam Davis
2025-11-16  8:21   ` syzbot
2025-11-16  8:29 ` Edward Adam Davis
2025-11-16  8:54   ` syzbot
2025-11-16  9:04 ` [PATCH] Bluetooth: hci_sock: Prevent race in socket write iter and sock bind Edward Adam Davis
2025-11-16  9:35   ` bluez.test.bot
2025-11-19 14:30   ` 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=176356260726.811862.764219010634757763.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=eadavis@qq.com \
    --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=netdev@vger.kernel.org \
    --cc=syzbot+9aa47cd4633a3cf92a80@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.