From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] a53f4a: bap: Fix use-after-free of device referenced by se...
Date: Fri, 18 Sep 2026 17:29:14 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1169068/000000-a53f4a@github.com> (raw)
Branch: refs/heads/1169068
Home: https://github.com/bluez/bluez
Commit: a53f4a113e82bceb82f09dad1189030ad725165d
https://github.com/bluez/bluez/commit/a53f4a113e82bceb82f09dad1189030ad725165d
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-09-19 (Sat, 19 Sep 2026)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
bap: Fix use-after-free of device referenced by session
bap_attached() creates bap_data that are not bound to btd_service, and
can outlive the device (eg if ATT POLLHUP -> bap_detached is late).
This then crashes when accessing bap_data::device later.
Fix by having bap_data hold btd_device_ref(). This is similar to what
avdtp.c etc. do.
Remove no-op assign to ep->data->device in ep_register_bcast() +
bap_bcast_probe() -- these just assign the same device pointer.
Log:
ERROR: AddressSanitizer: heap-use-after-free on address 0x7d6513de0208
READ of size 8 at 0x7d6513de0208 thread T0
#0 0x5594209b7e9b in device_get_adapter src/device.c:6917
#1 0x55942086020e in find_cig_session profiles/audio/bap.c:2500
#2 0x559420a3f070 in queue_find src/shared/queue.c:230
#3 0x559420866cd3 in find_cig_enumerate profiles/audio/bap.c:2539
#4 0x559420866cd3 in bap_update_cigs_cb profiles/audio/bap.c:2688
#5 0x7ff515a46b9a
#6 0x7ff515a481d6
#7 0x7ff515a48576 in g_main_loop_run
#8 0x559420b9af48 in mainloop_run src/shared/mainloop-glib.c:65
#9 0x559420b9b87a in mainloop_run_with_signal src/shared/mainloop-notify.c:196
#10 0x5594207192ba in main src/main.c:1713
0x7d6513de0208 is located 392 bytes inside of 752-byte region [0x7d6513de0080,0x7d6513de0370)
freed by thread T0 here:
#0 0x7ff515d2d3ff in free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:51
#1 0x559420a29a39 in remove_interface gdbus/object.c:742
previously allocated by thread T0 here:
#0 0x7ff515d2e40f in calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:74
#1 0x5594209cd302 in device_new src/device.c:5008
Assisted-by: opencode:qwen3.8-flash-next
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-09-19 0:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1169068/000000-a53f4a@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@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