[bluez/bluez] e0f608: shared/rap: fix use of uninitialized value

[bluez/bluez] e0f608: shared/rap: fix use of uninitialized value

[BluezTestBot]

  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