From: Paul Menzel <pmenzel@molgen.mpg.de>
To: WenTao Liang <vulab@iscas.ac.cn>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] fix: net/bluetooth: iso_conn_del: extra iso_conn_put on iso_sock_hold failure path
Date: Fri, 26 Jun 2026 15:12:51 +0200 [thread overview]
Message-ID: <1069f872-ef51-4e41-8284-419e751c4b3f@molgen.mpg.de> (raw)
In-Reply-To: <20260626115312.33528-1-vulab@iscas.ac.cn>
Dear Wen Tao,
Thank you for your patch. Some formalities:
The prefixes are well defined, and `fix:` will make the CI fail. Also,
it’d be great if you removed the tripple space in the summary/title, and
made it a statement by adding a verb in imperative mood. Maybe:
Bluetooth: Fix extra iso_conn_put on iso_sock_hold failure path
Am 26.06.26 um 13:53 schrieb WenTao Liang:
> In iso_conn_del(), iso_conn_hold_unless_zero() acquires a temporary
> reference which is correctly balanced by iso_conn_put() at line 279. When
> iso_sock_hold() returns NULL (sk == NULL), an additional
> iso_conn_put(conn) is called, dropping hcon's reference to conn too
> early. The caller (e.g., hci_conn_del) will later also iso_conn_put(),
> causing a double-free or use-after-free.
It’s uncommon to indent any lines of a paragraph. I recommend to remove
it, and then each line also fits in 75 characters.
> Remove the extra iso_conn_put(conn) on the sk == NULL path.
Out of curiosity: Do you have a reproducer?
> Cc: stable@vger.kernel.org
> Fixes: dc26097bdb86 ("Bluetooth: ISO: Use kref to track lifetime of iso_conn")
> Signed-off-by: WenTao Liang <vulab@iscas.ac.cn>
> ---
> net/bluetooth/iso.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/net/bluetooth/iso.c b/net/bluetooth/iso.c
> index 3abd8111dda8..99755671e469 100644
> --- a/net/bluetooth/iso.c
> +++ b/net/bluetooth/iso.c
> @@ -278,10 +278,8 @@ static void iso_conn_del(struct hci_conn *hcon, int err)
> iso_conn_unlock(conn);
> iso_conn_put(conn);
>
> - if (!sk) {
> - iso_conn_put(conn);
> + if (!sk)
> return;
> - }
>
> lock_sock(sk);
> iso_sock_clear_timer(sk);
gemini/gemini-3.1-pro-preview has two comments [1].
Kind regards,
Paul
[1]:
https://sashiko.dev/#/patchset/20260626115312.33528-1-vulab%40iscas.ac.cn
next prev parent reply other threads:[~2026-06-26 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 11:53 WenTao Liang
2026-06-26 13:12 ` Paul Menzel [this message]
2026-06-28 3:54 ` WenTao Liang
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=1069f872-ef51-4e41-8284-419e751c4b3f@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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
all inboxes | Powered by JetHome®