From: Arkadiusz Bokowy <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 8c6057: lib: Fix out-of-bounds write when concatenating co...
Date: Mon, 25 Aug 2025 08:33:45 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/995289/000000-8c6057@github.com> (raw)
Branch: refs/heads/995289
Home: https://github.com/bluez/bluez
Commit: 8c6057e570e6eccbf3a6f565fbc2d55ae9f19116
https://github.com/bluez/bluez/commit/8c6057e570e6eccbf3a6f565fbc2d55ae9f19116
Author: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
Date: 2025-08-25 (Mon, 25 Aug 2025)
Changed paths:
M lib/bluetooth/hci.c
M lib/bluetooth/hci_lib.h
Log Message:
-----------
lib: Fix out-of-bounds write when concatenating commands
This commit fixes the hci_commandstostr() command by writing new line
character in place of trailing space when wrapping long lines. Previous
approach was to append new line character to existing string, which
caused buffer overflow when there was more than 9 lines in the output
string.
Also, the last trailing space is removed in order to return
trailing-spaces-free string to the caller.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-08-25 15:33 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/995289/000000-8c6057@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;
as well as URLs for NNTP newsgroup(s).