From: patchwork-bot+bluetooth@kernel.org
To: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
chethan.tumkur.narayan@intel.com, kiran.k@intel.com
Subject: Re: [PATCH v1 0/3] Bluetooth: btintel: security fixes
Date: Tue, 22 Sep 2026 15:00:06 +0000 [thread overview]
Message-ID: <179008920691.4126096.131663704074702408.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1790053452.git.chandrashekar.devegowda@intel.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 22 Sep 2026 12:10:19 +0530 you wrote:
> Three small, independent fixes found by an internal audit of the Intel
> Bluetooth drivers:
>
> 1. btintel: bound the "Exception info" print, which reads past a
> controller-supplied buffer that is not NUL-terminated.
> 2. btintel_pcie: widen plen to u32 so HDR_SIZE + dlen cannot wrap
> and defeat the RX length check.
> 3. btintel_pcie: reject TX packets larger than the DMA buffer
> before they reach the memcpy() in the TX submit path.
>
> [...]
Here is the summary with links:
- [v1,1/3] Bluetooth: btintel: fix buffer over-read in btintel_hw_error()
https://git.kernel.org/bluetooth/bluetooth-next/c/4145a13c1a04
- [v1,2/3] Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame()
https://git.kernel.org/bluetooth/bluetooth-next/c/6d21e89e6977
- [v1,3/3] Bluetooth: btintel_pcie: reject oversized TX packets in send_frame()
https://git.kernel.org/bluetooth/bluetooth-next/c/2b036342b623
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-22 15:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 6:40 [PATCH v1 0/3] Bluetooth: btintel: security fixes Chandrashekar Devegowda
2026-09-22 6:40 ` [PATCH v1 1/3] Bluetooth: btintel: fix buffer over-read in btintel_hw_error() Chandrashekar Devegowda
2026-09-22 7:41 ` Bluetooth: btintel: security fixes bluez.test.bot
2026-09-22 6:40 ` [PATCH v1 2/3] Bluetooth: btintel_pcie: fix plen overflow in btintel_pcie_recv_frame() Chandrashekar Devegowda
2026-09-22 6:40 ` [PATCH v1 3/3] Bluetooth: btintel_pcie: reject oversized TX packets in send_frame() Chandrashekar Devegowda
2026-09-22 15: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=179008920691.4126096.131663704074702408.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.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 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.