From: "github-actions[bot]" <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] d925af: btio: fix range validation of security level
Date: Tue, 08 Jul 2025 00:45:23 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/979927/000000-c74271@github.com> (raw)
Branch: refs/heads/979927
Home: https://github.com/bluez/bluez
Commit: d925aff1485cf33d60557efd44b3db45b2f84241
https://github.com/bluez/bluez/commit/d925aff1485cf33d60557efd44b3db45b2f84241
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 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: 0912ffde6a01d5e787b6883201c160c421fd1858
https://github.com/bluez/bluez/commit/0912ffde6a01d5e787b6883201c160c421fd1858
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 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: 4f17104ab7493de93ee4d1db428ff01c05126496
https://github.com/bluez/bluez/commit/4f17104ab7493de93ee4d1db428ff01c05126496
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 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: 1c6ef345ea4bd569959b4333e2dbeee799e398a1
https://github.com/bluez/bluez/commit/1c6ef345ea4bd569959b4333e2dbeee799e398a1
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M tools/isotest.c
Log Message:
-----------
isotest: close fd after sending when nconn=1
Commit: 7187338cb0f39bc193f11135cb64a5fede8b8126
https://github.com/bluez/bluez/commit/7187338cb0f39bc193f11135cb64a5fede8b8126
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 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.
Commit: 03ca538c8ff3fc21b734c7d10048007bcecf9cb9
https://github.com/bluez/bluez/commit/03ca538c8ff3fc21b734c7d10048007bcecf9cb9
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M profiles/audio/bap.c
Log Message:
-----------
profiles/audio: fix memleak of bt_bap
Make failure branches deallocate memory before leaving.
Commit: 0ac037158b21dd0e67c4e337385276089d42bcdb
https://github.com/bluez/bluez/commit/0ac037158b21dd0e67c4e337385276089d42bcdb
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
src/shared: fix memleak
Commit: f75df3ae83d1288e3ef68016d18a1550fd0df109
https://github.com/bluez/bluez/commit/f75df3ae83d1288e3ef68016d18a1550fd0df109
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M src/shared/bap.c
M src/shared/gatt-db.c
Log Message:
-----------
src/shared: move null checks before dereferencing
Commit: c9f54bddda9ceb5d057bbc08a7271d71e84dd15b
https://github.com/bluez/bluez/commit/c9f54bddda9ceb5d057bbc08a7271d71e84dd15b
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M tools/isotest.c
Log Message:
-----------
isotest: remove repeating conditions
Commit: 188ef95b3ffed41e7da72ce0bb09fe2a7a60a777
https://github.com/bluez/bluez/commit/188ef95b3ffed41e7da72ce0bb09fe2a7a60a777
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M profiles/audio/bass.c
M profiles/audio/transport.c
Log Message:
-----------
profiles/audio: fix io_unlink args order
Seems like a breaking bug. Analogous to bt_bap_stream_io_link,
but there the order is correct.
Commit: c74271b46eb791b341aaf9d1fe3dadc9f797557c
https://github.com/bluez/bluez/commit/c74271b46eb791b341aaf9d1fe3dadc9f797557c
Author: Ismagil Iskakov <i.iskakov@omp.ru>
Date: 2025-07-08 (Tue, 08 Jul 2025)
Changed paths:
M src/plugin.c
Log Message:
-----------
src/plugin: fix args order
According to other functions and arguments usage, the
case with external_plugin_init seems to be erroneous.
Compare: https://github.com/bluez/bluez/compare/d925aff1485c%5E...c74271b46eb7
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-08 7:45 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/979927/000000-c74271@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