From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com, linux-kernel@vger.kernel.org,
syzbot+9c40ad7c6ed7165e46e8@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH 1/2] Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
Date: Tue, 04 Aug 2026 17:40:06 +0000 [thread overview]
Message-ID: <178586520639.3702995.4820111211961794827.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <a672a4ee3d24c93156c51ef84ca4dc3364a18109.1785609341.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 1 Aug 2026 21:37:23 +0300 you wrote:
> hci_conn::l2cap_data is accessed without locks in l2cap_disconn_ind via
> hci_conn_timeout (disc_work) -> hci_proto_disconn_ind ->
> l2cap_disconn_ind. This is UAF if the l2cap_conn is deleted
> concurrently.
>
> disc_work is disabled sync in hci_conn_del(), so we cannot take
> hci_dev_lock in disc_work.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind
https://git.kernel.org/bluetooth/bluetooth-next/c/b974e13aafe9
- [2/2] Bluetooth: add annotations for l2cap_data locking context
https://git.kernel.org/bluetooth/bluetooth-next/c/d740cf77461a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-04 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 18:37 [PATCH 1/2] Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind Pauli Virtanen
2026-08-01 18:37 ` [PATCH 2/2] Bluetooth: add annotations for l2cap_data locking context Pauli Virtanen
2026-08-01 19:22 ` [1/2] Bluetooth: L2CAP: use proto_lock for l2cap_data to fix l2cap_disconn_ind bluez.test.bot
2026-08-04 17:40 ` 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=178586520639.3702995.4820111211961794827.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pav@iki.fi \
--cc=syzbot+9c40ad7c6ed7165e46e8@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.