From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: SCO: Fix UAF on sco_sock_timeout
Date: Wed, 23 Oct 2024 14:10:29 +0000 [thread overview]
Message-ID: <172969262900.1607474.17842690282865996474.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241022203421.2126673-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 22 Oct 2024 16:34:20 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> conn->sk maybe have been unlinked/freed while waiting for sco_conn_lock
> so this checks if the conn->sk is still valid by checking if it part of
> sco_sk_list.
>
> Reported-by: syzbot+4c0d0c4cde787116d465@syzkaller.appspotmail.com
> Tested-by: syzbot+4c0d0c4cde787116d465@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=4c0d0c4cde787116d465
> Fixes: ba316be1b6a0 ("Bluetooth: schedule SCO timeouts with delayed_work")
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: SCO: Fix UAF on sco_sock_timeout
https://git.kernel.org/bluetooth/bluetooth-next/c/300b75192c4d
- [v2,2/2] Bluetooth: ISO: Fix UAF on iso_sock_timeout
https://git.kernel.org/bluetooth/bluetooth-next/c/fb4560832d4c
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:[~2024-10-23 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 20:34 [PATCH v2 1/2] Bluetooth: SCO: Fix UAF on sco_sock_timeout Luiz Augusto von Dentz
2024-10-22 20:34 ` [PATCH v2 2/2] Bluetooth: ISO: Fix UAF on iso_sock_timeout Luiz Augusto von Dentz
2024-10-23 14: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=172969262900.1607474.17842690282865996474.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.