From: patchwork-bot+bluetooth@kernel.org
To: Dudu Lu <phx0fer@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
luiz.dentz@gmail.com
Subject: Re: [PATCH] Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling
Date: Wed, 15 Apr 2026 21:00:04 +0000 [thread overview]
Message-ID: <177628680480.2439002.16377687042419433423.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260415093953.39340-1-phx0fer@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 15 Apr 2026 17:39:53 +0800 you wrote:
> In bnep_rx_frame(), the BNEP_FILTER_NET_TYPE_SET and
> BNEP_FILTER_MULTI_ADDR_SET extension header parsing has two bugs:
>
> 1) The 2-byte length field is read with *(u16 *)(skb->data + 1), which
> performs a native-endian read. The BNEP protocol specifies this field
> in big-endian (network byte order), and the same file correctly uses
> get_unaligned_be16() for the identical fields in
> bnep_ctrl_set_netfilter() and bnep_ctrl_set_mcfilter().
>
> [...]
Here is the summary with links:
- Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling
https://git.kernel.org/bluetooth/bluetooth-next/c/5843e5ef062a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-15 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 9:39 [PATCH] Bluetooth: bnep: fix incorrect length parsing in bnep_rx_frame() extension handling Dudu Lu
2026-04-15 10:22 ` bluez.test.bot
2026-04-15 21: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=177628680480.2439002.16377687042419433423.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=phx0fer@gmail.com \
/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