From: patchwork-bot+bluetooth@kernel.org
To: Hyunwoo Kim <v4bel@theori.io>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, imv4bel@gmail.com,
johan.hedberg@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg
Date: Fri, 15 Dec 2023 16:00:25 +0000 [thread overview]
Message-ID: <170265602589.22720.8309217075489314107.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231209105518.GA408904@v4bel-B760M-AORUS-ELITE-AX>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 9 Dec 2023 05:55:18 -0500 you wrote:
> This can cause a race with bt_sock_ioctl() because
> bt_sock_recvmsg() gets the skb from sk->sk_receive_queue
> and then frees it without holding lock_sock.
> A use-after-free for a skb occurs with the following flow.
> ```
> bt_sock_recvmsg() -> skb_recv_datagram() -> skb_free_datagram()
> bt_sock_ioctl() -> skb_peek()
> ```
> Add lock_sock to bt_sock_recvmsg() to fix this issue.
>
> [...]
Here is the summary with links:
- [v2] Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg
https://git.kernel.org/bluetooth/bluetooth-next/c/63b55655d30b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-15 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 10:55 [PATCH v2] Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg Hyunwoo Kim
2023-12-09 11:30 ` [v2] " bluez.test.bot
2023-12-15 16:00 ` patchwork-bot+bluetooth [this message]
2024-02-22 11:23 ` [PATCH v2] " Martyn Welch
2024-04-22 23:49 ` Hyunwoo Kim
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=170265602589.22720.8309217075489314107.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=imv4bel@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=v4bel@theori.io \
/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 NNTP newsgroup(s).