From: patchwork-bot+bluetooth@kernel.org
To: Hui Peng <benquike@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough
Date: Mon, 21 Sep 2026 14:10:13 +0000 [thread overview]
Message-ID: <178999981314.3047822.6059852336450565758.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260919221738.3708655-1-benquike@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, 19 Sep 2026 22:17:38 +0000 you wrote:
> Fix multiple out-of-bounds reads in Bluetooth BNEP frame processing:
>
> 1. In bnep_rx_frame() and bnep_ctrl_frame() (net/bluetooth/bnep/core.c),
> use pskb_may_pull() to verify the BNEP header, control type byte,
> filter count, and extension headers exist before reading them, and
> return 0 after handling BNEP_CONTROL instead of falling through to
> Ethernet frame submission when no extension headers follow.
> 2. In bnep_net_xmit() (net/bluetooth/bnep/netdev.c), verify skb->len >=
> ETH_HLEN with pskb_may_pull() before reading the 14-byte Ethernet
> header to prevent an out-of-bounds heap read and infoleak on short
> AF_PACKET TX frames.
>
> [...]
Here is the summary with links:
- Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough
https://git.kernel.org/bluetooth/bluetooth-next/c/f0ca020cbb9b
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-09-21 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 22:17 [PATCH] Bluetooth: bnep: fix out-of-bounds reads on short RX/TX frames and control fallthrough Hui Peng
2026-09-20 0:20 ` bluez.test.bot
2026-09-21 14:10 ` 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=178999981314.3047822.6059852336450565758.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=benquike@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.