From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 9e76fb: bthost: Fix crash on l2cap_ecred_conn_rsp
Date: Mon, 13 Oct 2025 10:44:40 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/3e17f8-9e76fb@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 9e76fb9f6ce830cebb71a0b54a662ea8bb50bd54
https://github.com/bluez/bluez/commit/9e76fb9f6ce830cebb71a0b54a662ea8bb50bd54
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2025-10-13 (Mon, 13 Oct 2025)
Changed paths:
M emulator/bthost.c
Log Message:
-----------
bthost: Fix crash on l2cap_ecred_conn_rsp
This fixes the following crash:
Invalid read of size 2
at 0x4019907: l2cap_ecred_conn_rsp (bthost.c:2554)
by 0x4019907: l2cap_le_sig (bthost.c:2650)
by 0x4019907: process_l2cap (bthost.c:3137)
by 0x401BBA3: process_acl (bthost.c:3242)
by 0x401BBA3: bthost_receive_h4 (bthost.c:3402)
by 0x4008835: receive_bthost (bluetooth.c:2989)
by 0x493B862: ??? (in /usr/lib64/libglib-2.0.so.0.8400.4)
by 0x49447A7: ??? (in /usr/lib64/libglib-2.0.so.0.8400.4)
by 0x4944A4E: g_main_loop_run (in /usr/lib64/libglib-2.0.so.0.8400.4)
by 0x402645D: mainloop_run (mainloop-glib.c:65)
by 0x4026A34: mainloop_run_with_signal (mainloop-notify.c:196)
by 0x4025C55: tester_run (tester.c:1084)
by 0x4002A7B: main (l2cap-tester.c:2799)
Address 0x400bc02a4 is not stack'd, malloc'd or (recently) free'd
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-13 17:44 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/3e17f8-9e76fb@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