From: Pauli Virtanen <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 04d044: shared/bap: check pac cc and metadata length befor...
Date: Sat, 11 Oct 2025 11:54:47 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1010380/000000-04d044@github.com> (raw)
Branch: refs/heads/1010380
Home: https://github.com/bluez/bluez
Commit: 04d044e80dc9872c1705703c73df71c79a8560c9
https://github.com/bluez/bluez/commit/04d044e80dc9872c1705703c73df71c79a8560c9
Author: Pauli Virtanen <pav@iki.fi>
Date: 2025-10-11 (Sat, 11 Oct 2025)
Changed paths:
M src/shared/bap.c
Log Message:
-----------
shared/bap: check pac cc and metadata length before use
Don't read past buffer end if device provided bogus values for PAC
caps/metadata lengths.
Use iov pull properly, and also check metadata LTV validity.
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-10-11 18:54 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/1010380/000000-04d044@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