From: patchwork-bot+bluetooth@kernel.org
To: Muhammad Bilal <meatuni001@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, stable@vger.kernel.org,
marcel@holtmann.org, luiz.dentz@gmail.com
Subject: Re: [PATCH 1/2] Bluetooth: ISO: fix UAF in iso_recv_frame
Date: Wed, 27 May 2026 20:50:07 +0000 [thread overview]
Message-ID: <177991500739.647444.13417496259944971755.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260527045919.39077-1-meatuni001@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 27 May 2026 04:59:17 +0000 you wrote:
> iso_recv_frame reads conn->sk under iso_conn_lock but releases the lock
> before using sk, with no reference held. A concurrent iso_sock_kill()
> can free sk in that window, causing use-after-free on sk->sk_state and
> sock_queue_rcv_skb().
>
> Fix by replacing the bare pointer read with iso_sock_hold(conn), which
> calls sock_hold() while the spinlock is held, atomically elevating the
> refcount before the lock drops. Add a drop_put label so sock_put() is
> called on all exit paths where the hold succeeded.
>
> [...]
Here is the summary with links:
- [1/2] Bluetooth: ISO: fix UAF in iso_recv_frame
https://git.kernel.org/bluetooth/bluetooth-next/c/7e3545cc3d1a
- [2/2] Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock
https://git.kernel.org/bluetooth/bluetooth-next/c/7978ae58aafb
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-05-27 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 4:59 [PATCH 1/2] Bluetooth: ISO: fix UAF in iso_recv_frame Muhammad Bilal
2026-05-27 4:59 ` [PATCH 2/2] Bluetooth: ISO: serialize iso_sock_clear_timer with socket lock Muhammad Bilal
2026-05-27 6:41 ` [1/2] Bluetooth: ISO: fix UAF in iso_recv_frame bluez.test.bot
2026-05-27 20:50 ` 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=177991500739.647444.13417496259944971755.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=meatuni001@gmail.com \
--cc=stable@vger.kernel.org \
/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