From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] e0f608: shared/rap: fix use of uninitialized value
Date: Mon, 18 May 2026 15:55:55 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/45e66b-757cd9@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: e0f608c05f9a007b9867c53234465f2b1fb0d8fa
https://github.com/bluez/bluez/commit/e0f608c05f9a007b9867c53234465f2b1fb0d8fa
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-18 (Mon, 18 May 2026)
Changed paths:
M src/shared/rap.c
Log Message:
-----------
shared/rap: fix use of uninitialized value
Fix error handling in send_ras_segment_data
Commit: dc07b3d54b801dea84e82397057071a824a38500
https://github.com/bluez/bluez/commit/dc07b3d54b801dea84e82397057071a824a38500
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-18 (Mon, 18 May 2026)
Changed paths:
M lib/bluetooth/sdp.c
Log Message:
-----------
sdp: Fix integer overflow in sdp_extract_seqtype
Check uint32_t value does not overflow int range.
Link: https://lore.kernel.org/linux-bluetooth/ygH6bncNsvf-0Hco92Ae11Lw8-jOfekFO6O3bUvFK8w0DTueny_rwJIF6ffZg2G_XCB4v8h8xRIcAL2b_KwaweNcGa231ZQDHCMpzyvR5i8=@fluentlogic.org/
Commit: 1e0688e8bfdaf20a34174dcd7ec855adb8e18216
https://github.com/bluez/bluez/commit/1e0688e8bfdaf20a34174dcd7ec855adb8e18216
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-05-18 (Mon, 18 May 2026)
Changed paths:
M src/main.conf
Log Message:
-----------
main.conf: fix unintentionally set value
Commit 31e4fb1498f ("monitor: Add decoding support for HIDS 1.1 flags
and attributes") unintentionally set a non-default value in main.conf.
Restore the value back.
Commit: 757cd98f4186e6e1e38b0a36539b78a20e93b5bf
https://github.com/bluez/bluez/commit/757cd98f4186e6e1e38b0a36539b78a20e93b5bf
Author: Zhao Dongdong <zhaodongdong@kylinos.cn>
Date: 2026-05-18 (Mon, 18 May 2026)
Changed paths:
M src/device.c
Log Message:
-----------
device: fix inverted NULL check in gatt_db clone
gatt_db_clone() returns NULL on failure so the condition was inverted.
With the old check a successful clone (non-NULL) would return false and
skip swapping the device's GATT database, while a failure (NULL) would
fall through and dereference a NULL pointer a few lines below.
Fix by negating the condition: only bail out early if the clone failed;
proceed with the swap when the clone actually succeeds.
Compare: https://github.com/bluez/bluez/compare/45e66b1c4aed...757cd98f4186
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-05-18 22:55 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/master/45e66b-757cd9@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