From: Tom Catshoek <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 48278c: adapter: Fix crash on UUID discovery filter match
Date: Thu, 09 Jul 2026 07:03:31 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1124682/000000-48278c@github.com> (raw)
Branch: refs/heads/1124682
Home: https://github.com/bluez/bluez
Commit: 48278c8a0ecf28a2c51f091dc86cc350457125b6
https://github.com/bluez/bluez/commit/48278c8a0ecf28a2c51f091dc86cc350457125b6
Author: Tom Catshoek <tomcatshoek@zeelandnet.nl>
Date: 2026-07-09 (Thu, 09 Jul 2026)
Changed paths:
M src/adapter.c
Log Message:
-----------
adapter: Fix crash on UUID discovery filter match
is_filter_match() looks up each discovery-filter UUID in the queue of
services parsed from a device advertisement. When that services list was
migrated from a GSList to a struct queue, the queue_find() call kept
GLib's g_slist_find_custom() argument order, passing the UUID string
where queue_find() expects a match function and the comparison function
where it expects the match data.
As a result queue_find() calls the UUID string as if it were a function,
jumping into non-executable heap and crashing bluetoothd with SIGSEGV as
soon as an advertisement matches a UUID filter configured via
SetDiscoveryFilter.
Add a queue_match_func_t helper and pass the arguments in the correct
order.
Fixes: https://github.com/bluez/bluez/issues/2282
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-07-09 14:03 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/1124682/000000-48278c@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