From: patchwork-bot+bluetooth@kernel.org
To: Tao Cai <294305068@qq.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ] device: Fix NULL pointer dereference in dev_property_get_uuids
Date: Tue, 22 Sep 2026 15:20:05 +0000 [thread overview]
Message-ID: <179009040515.4135593.12444042145585528858.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_27EA4A683B87E3DCF400C26D990DD9364507@qq.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 22 Sep 2026 11:10:17 +0800 you wrote:
> The bluetoothd process crashes during D-Bus property serialization when
> the device UUID list contains a NULL entry. Add a NULL check before
> calling dbus_message_iter_append_basic().
>
> ---
> Crash Stack Trace (BlueZ 5.71 AArch64):
> #0 0x0000ffff8ecfbe98 in ??? () at /lib/aarch64-linux-gnu/libc.so.6
> #1 0x0000ffff8ecfe548 in ??? () at /lib/aarch64-linux-gnu/libc.so.6
> #2 0x0000ffff8ecff120 in ??? () at /lib/aarch64-linux-gnu/libc.so.6
> #3 0x0000ffff8ed005c8 in realloc () at /lib/aarch64-linux-gnu/libc.so.6
> #4 0x0000ffff8f250204 in ??? () at /lib/aarch64-linux-gnu/libdbus-1.so.3
> #5 0x0000ffff8f251c34 in _dbus_string_copy_len () at /lib/aarch64-linux-gnu/libdbus-1.so.3
> #6 0x0000ffff8f254294 in ??? () at /lib/aarch64-linux-gnu/libdbus-1.so.3
> #7 0x0000ffff8f23f968 in _dbus_type_writer_write_basic () at /lib/aarch64-linux-gnu/libdbus-1.so.3
> #8 0x0000ffff8f243208 in dbus_message_iter_append_basic () at /lib/aarch64-linux-gnu/libdbus-1.so.3
> #9 0x0000aaaabe2f64d0 in dev_property_get_uuids (property=<optimized out>, iter=0xffffd510cf28, data=0xaaaac18514e0) at src/device.c:1339
> ...
> #21 main (argc=<optimized out>, argv=<optimized out>) at src/main.c:1456
>
> [...]
Here is the summary with links:
- [BlueZ] device: Fix NULL pointer dereference in dev_property_get_uuids
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f26da4389e2d
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-09-22 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 3:10 [PATCH BlueZ] device: Fix NULL pointer dereference in dev_property_get_uuids Tao Cai
2026-09-22 6:58 ` [BlueZ] " bluez.test.bot
2026-09-22 15:20 ` 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=179009040515.4135593.12444042145585528858.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=294305068@qq.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.