From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Ali Ahmet Memis <ali@iusegentoo.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
johan.hedberg@intel.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btintel: Bound exception info print to the received length
Date: Fri, 14 Aug 2026 11:36:58 +0200 [thread overview]
Message-ID: <080b7ab7-15ac-403f-9997-3dfb85c8efbf@molgen.mpg.de> (raw)
In-Reply-To: <20260814080123.902388-1-ali@iusegentoo.com>
Dear Ali,
Thank you for your patch.
Am 14.08.26 um 10:01 schrieb Ali Ahmet Memis:
> btintel_hw_error() validates that the Intel exception info response is
> exactly 13 bytes, and then prints the 12 bytes following the status byte
> with a plain "%s". Nothing validates that those 12 bytes contain a NUL,
> so the conversion can run past the end of the received response and into
> whatever follows it in the skb.
>
> Bound the conversion to the length that was actually received.
>
> Fixes: 973bb97e5aee ("Bluetooth: btintel: Add generic function for handling hardware errors")
> Signed-off-by: Ali Ahmet Memis <ali@iusegentoo.com>
> ---
> drivers/bluetooth/btintel.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/bluetooth/btintel.c b/drivers/bluetooth/btintel.c
> index bf567b7c5f00..4112f39f251f 100644
> --- a/drivers/bluetooth/btintel.c
> +++ b/drivers/bluetooth/btintel.c
> @@ -288,7 +288,9 @@ void btintel_hw_error(struct hci_dev *hdev, u8 code)
> goto unlock;
> }
>
> - bt_dev_err(hdev, "Exception info %s", (char *)(skb->data + 1));
> + /* The exception info field is not guaranteed to be NUL terminated */
> + bt_dev_err(hdev, "Exception info %.*s", (int)(skb->len - 1),
> + (char *)(skb->data + 1));
>
> kfree_skb(skb);
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
PS: gemini/gemini-3.1-pro-preview found also other occurrences [1].
[1]:
https://sashiko.dev/#/patchset/20260814080123.902388-1-ali%40iusegentoo.com
prev parent reply other threads:[~2026-08-14 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 8:01 [PATCH] Bluetooth: btintel: Bound exception info print to the received length Ali Ahmet Memis
2026-08-14 8:38 ` bluez.test.bot
2026-08-14 9:36 ` Paul Menzel [this message]
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=080b7ab7-15ac-403f-9997-3dfb85c8efbf@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=ali@iusegentoo.com \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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