All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Aldo Ariel Panzardo <qwe.aldo@gmail.com>
Cc: luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_sock: validate event length before filtering
Date: Wed, 16 Sep 2026 18:00:07 +0000	[thread overview]
Message-ID: <178958160713.2777538.3303073061457173615.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915160307.3106955-1-qwe.aldo@gmail.com>

Hello:

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

On Tue, 15 Sep 2026 13:03:07 -0300 you wrote:
> is_filtered_packet() reads the event code from skb->data[0] without first
> checking that the skb is nonempty. When an opcode filter is configured,
> it also reads the command opcode at offsets 3 or 4 without checking that
> a Command Complete or Command Status event is long enough.
> 
> hci_send_to_sock() invokes the filter before hci_event_packet() validates
> the event header. A malformed event supplied by a controller or a vhci
> device can therefore cause an out-of-bounds read.
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_sock: validate event length before filtering
    https://git.kernel.org/bluetooth/bluetooth-next/c/b0a6cf99afd5

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-09-16 18:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 16:03 [PATCH] Bluetooth: hci_sock: validate event length before filtering Aldo Ariel Panzardo
2026-09-15 17:37 ` bluez.test.bot
2026-09-16 18:00 ` 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=178958160713.2777538.3303073061457173615.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=qwe.aldo@gmail.com \
    --cc=stable@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 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.