From: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: chethan.tumkur.narayan@intel.com, kiran.k@intel.com,
Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
Subject: [PATCH v1 0/3] Bluetooth: btintel: security fixes
Date: Tue, 22 Sep 2026 12:10:19 +0530 [thread overview]
Message-ID: <cover.1790053452.git.chandrashekar.devegowda@intel.com> (raw)
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.
All three pass checkpatch --strict.
Chandrashekar Devegowda (3):
Bluetooth: btintel: fix buffer over-read in btintel_hw_error()
Bluetooth: btintel_pcie: fix plen overflow in
btintel_pcie_recv_frame()
Bluetooth: btintel_pcie: reject oversized TX packets in send_frame()
drivers/bluetooth/btintel.c | 3 ++-
drivers/bluetooth/btintel_pcie.c | 12 +++++++++++-
2 files changed, 13 insertions(+), 2 deletions(-)
base-commit: 06d991977eeff5d51327e1e64889e70658e8f7ff
--
2.43.0
next reply other threads:[~2026-09-22 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 6:40 Chandrashekar Devegowda [this message]
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 ` [PATCH v1 0/3] Bluetooth: btintel: security fixes patchwork-bot+bluetooth
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=cover.1790053452.git.chandrashekar.devegowda@intel.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox