From: Bastien Nocera <hadess@hadess.net>
To: BUGPWN <vuln.bugpwn@gmail.com>, security@bluez.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Use-after-free in avdtp_connect_cb() (profiles/audio/avdtp.c) via unreferenced transport connect callback
Date: Wed, 26 Aug 2026 15:21:48 +0200 [thread overview]
Message-ID: <06aa2f63a02022e2e34879cd8615dbc16c8619d3.camel@hadess.net> (raw)
In-Reply-To: <CAOZc4ksrOkoK8u3Mm5C5bGH_xNL1tn15Pq68oCtijoFpxSGBFA@mail.gmail.com>
On Tue, 2026-08-25 at 12:36 +0100, BUGPWN wrote:
> Summary
> -------
>
> profiles/audio/avdtp.c contains a use-after-free in
> avdtp_connect_cb(), reachable when
> an AVDTP session is torn down (e.g. the remote peer closes the
> signaling channel) while
> an asynchronous transport channel connect, started by
> l2cap_connect(),
> is still in
> flight. The transport connect's callback is registered without a
> reference on the
> session object and without a destroy notifier, so it can fire after
> the session has
> already been freed.
>
> Also submitted via GitHub's private vulnerability reporting.
What's the link to that report?
>
<snip>
> Reproducing this over real L2CAP sockets and glib timing would
> require a virtual
> controller (vhci) and a fake peer (bthost/btdev) with precise
> two-channel timing.
Can this even be triggered without using vHCI?
Regards
prev parent reply other threads:[~2026-08-26 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 11:36 Use-after-free in avdtp_connect_cb() (profiles/audio/avdtp.c) via unreferenced transport connect callback BUGPWN
2026-08-26 13:21 ` Bastien Nocera [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=06aa2f63a02022e2e34879cd8615dbc16c8619d3.camel@hadess.net \
--to=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=security@bluez.org \
--cc=vuln.bugpwn@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox