From: BluezTestBot <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 80a6b9: btio: fix range validation of security level
Date: Wed, 09 Jul 2025 06:53:54 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/a3824b-09212f@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 80a6b91d758ac94d6b6d40250d68f06cd4a06097
https://github.com/bluez/bluez/commit/80a6b91d758ac94d6b6d40250d68f06cd4a06097
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-09 (Wed, 09 Jul 2025)
Changed paths:
M btio/btio.c
Log Message:
-----------
btio: fix range validation of security level
Arrays inside l2cap_set_lm/rfcomm_set_lm functions are of size 4,
but the bounds check allows the value 4 for 'level'.
Commit: 77932f2dac1af0506e289703e43e057d21c40fce
https://github.com/bluez/bluez/commit/77932f2dac1af0506e289703e43e057d21c40fce
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-09 (Wed, 09 Jul 2025)
Changed paths:
M profiles/audio/a2dp.c
M profiles/audio/avrcp.c
M profiles/audio/bass.c
Log Message:
-----------
profiles/audio: add nullity checks
Cover bass_setup unsuccessful search and btd_device_get_service.
This change is motivated by the other usages where checks for
NULL exist.
Commit: 9432bfe81afd177be2778c65b640658f88b7ef28
https://github.com/bluez/bluez/commit/9432bfe81afd177be2778c65b640658f88b7ef28
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-09 (Wed, 09 Jul 2025)
Changed paths:
M src/shared/bap.c
M src/shared/vcp.c
Log Message:
-----------
src/shared: add nullity checks
Check util_iov_pull_mem where iov len is not verified
beforehand. Check vcp_get_vcs for NULL.
These changes are based on other usages where those
checks exist.
Commit: 09212f9d110e268332041c6038895e581d73d4bd
https://github.com/bluez/bluez/commit/09212f9d110e268332041c6038895e581d73d4bd
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-09 (Wed, 09 Jul 2025)
Changed paths:
M obexd/client/transfer.c
Log Message:
-----------
obexd/client: fix err condition causing memleak
transfer_open returns 0 if an error occurs, condition corrected.
Compare: https://github.com/bluez/bluez/compare/a3824b4aac0e...09212f9d110e
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-09 13:53 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/a3824b-09212f@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 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.