All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Laxman Acharya Padhya <acharyalaxman8848@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_event: validate LE Set CIG Parameters response
Date: Tue, 04 Aug 2026 17:40:10 +0000	[thread overview]
Message-ID: <178586521063.3702995.14976898276396935564.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260801180952.52072-1-acharyalaxman8848@gmail.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Sat,  1 Aug 2026 23:54:52 +0545 you wrote:
> The Command Complete dispatch validates only the fixed part of the LE Set
> CIG Parameters response. After that part is pulled from the skb,
> hci_cc_le_set_cig_params() trusts num_handles and reads each entry in the
> trailing handle array.
> 
> Matching num_handles against the command's num_cis does not guarantee
> that the response contains the advertised handles. A truncated response
> from a malfunctioning controller can therefore make the handler read
> beyond the skb data.
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_event: validate LE Set CIG Parameters response
    https://git.kernel.org/bluetooth/bluetooth-next/c/bece7ec4e259

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-08-04 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01 18:09 [PATCH] Bluetooth: hci_event: validate LE Set CIG Parameters response Laxman Acharya Padhya
2026-08-01 19:23 ` bluez.test.bot
2026-08-04 17:40 ` patchwork-bot+bluetooth [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=178586521063.3702995.14976898276396935564.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=acharyalaxman8848@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.