From: Wouter <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 183f1a: shared/shell: Fix SIGSEGV on invalid input
Date: Thu, 19 Mar 2026 08:06:48 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1069318/000000-183f1a@github.com> (raw)
Branch: refs/heads/1069318
Home: https://github.com/bluez/bluez
Commit: 183f1ac1578b41868c56b5527139f27a2d04a2a0
https://github.com/bluez/bluez/commit/183f1ac1578b41868c56b5527139f27a2d04a2a0
Author: Wouter <wouter@xesxen.nl>
Date: 2026-03-19 (Thu, 19 Mar 2026)
Changed paths:
M src/shared/shell.c
Log Message:
-----------
shared/shell: Fix SIGSEGV on invalid input
This fixes a crash when handling "<space><tab>"
==3760495== Invalid read of size 1
==3760495== at 0x4902187: strcmp (vg_replace_strmem.c:941)
==3760495== by 0x4067408: menu_completion (shell.c:1126)
==3760495== by 0x40675DE: shell_completion (shell.c:1177)
==3760495== by 0x4B267AB: gen_completion_matches (complete.c:1282)
==3760495== by 0x4B2F8C1: rl_complete_internal (complete.c:2104)
==3760495== by 0x4B26B52: _rl_dispatch_subseq (readline.c:941)
==3760495== by 0x4B27B71: readline_internal_char (readline.c:690)
==3760495== by 0x4B48695: rl_callback_read_char (callback.c:275)
==3760495== by 0x40655F2: bt_shell_input_line (shell.c:309)
==3760495== by 0x406577E: input_read (shell.c:343)
==3760495== by 0x4068CB4: watch_callback (io-glib.c:173)
==3760495== by 0x49C1F4C: g_main_dispatch (gmain.c:3565)
==3760495== Address 0x0 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:[~2026-03-19 15:06 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/1069318/000000-183f1a@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