From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 11d05e: shared/ad: Fix not checking length on ad_replace_name
Date: Tue, 17 Mar 2026 09:07:22 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/a035be-11d05e@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 11d05ece674fa1a31da50bf505bf744628ad9078
https://github.com/bluez/bluez/commit/11d05ece674fa1a31da50bf505bf744628ad9078
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-03-16 (Mon, 16 Mar 2026)
Changed paths:
M src/shared/ad.c
Log Message:
-----------
shared/ad: Fix not checking length on ad_replace_name
iov may carry move then HCI_MAX_NAME_LENGTH in which case it is
truncated so it doesn't overflow utf8_name.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-03-17 16:07 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/a035be-11d05e@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