From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v4] Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync
Date: Wed, 16 Aug 2023 19:20:20 +0000 [thread overview]
Message-ID: <169221362095.4169.6105116612298394879.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230814190101.2302448-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 14 Aug 2023 12:01:01 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> Use-after-free can occur in hci_disconnect_all_sync if a connection is
> deleted by concurrent processing of a controller event.
>
> To prevent this the code now tries to iterate over the list backwards
> to ensure the links are cleanup before its parents, also it no longer
> relies on a cursor, instead it always uses the last element since
> hci_abort_conn_sync is guaranteed to call hci_conn_del.
>
> [...]
Here is the summary with links:
- [v4] Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync
https://git.kernel.org/bluetooth/bluetooth-next/c/45c37c4e9c9a
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:[~2023-08-16 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 19:01 [PATCH v4] Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync Luiz Augusto von Dentz
2023-08-14 19:39 ` [v4] " bluez.test.bot
2023-08-15 22:41 ` [PATCH v4] " Luiz Augusto von Dentz
2023-08-16 17:54 ` Pauli Virtanen
2023-08-16 17:59 ` Luiz Augusto von Dentz
2023-08-16 19:20 ` 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=169221362095.4169.6105116612298394879.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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.