From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 7d9c6f: emulator: bthost: don't crash on ecred_conn_req wi...
Date: Sat, 29 Aug 2026 17:47:23 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1153725/000000-80ad2f@github.com> (raw)
Branch: refs/heads/1153725
Home: https://github.com/bluez/bluez
Commit: 7d9c6f97282b702a2bf19cff70668183139f159b
https://github.com/bluez/bluez/commit/7d9c6f97282b702a2bf19cff70668183139f159b
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-08-30 (Sun, 30 Aug 2026)
Changed paths:
M emulator/bthost.c
Log Message:
-----------
emulator: bthost: don't crash on ecred_conn_req with too many scid
l2cap_ecred_conn_req() crashes if the request contains more SCID than
specification allows (5).
Respond 0x000C - All connections refused – invalid parameters to such
invalid requests.
Commit: 80ad2f628f4b568b8167fe763f9721f2f3c26587
https://github.com/bluez/bluez/commit/80ad2f628f4b568b8167fe763f9721f2f3c26587
Author: Pauli Virtanen <pav@iki.fi>
Date: 2026-08-30 (Sun, 30 Aug 2026)
Changed paths:
M tools/l2cap-tester.c
Log Message:
-----------
tools/l2cap-tester: add test for too many ECRED deferred sockets
Add test tries to trigger connection with 5+1 ECRED channels, and
require the last connect() shall fail with -EPROTO. On some kernels
this causes invalid ECRED REQ be sent with 6 SCID, and stack overwrite.
L2CAP Ext-Flowctl Client - Defer limit
Compare: https://github.com/bluez/bluez/compare/7d9c6f97282b%5E...80ad2f628f4b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-08-30 0:47 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/1153725/000000-80ad2f@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