From: ZhaoJinming <zhaojinming@uniontech.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
Paul Menzel <pmenzel@molgen.mpg.de>
Cc: linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] Bluetooth: btintel_pcie: Fix bounds checks in TX completion handler
Date: Thu, 20 Aug 2026 17:17:39 +0800 [thread overview]
Message-ID: <20260820-btintel_pcie_bounds_fixes-v1-2-c9dcd1ac8bf6@uniontech.com> (raw)
In-Reply-To: <20260820-btintel_pcie_bounds_fixes-v1-0-c9dcd1ac8bf6@uniontech.com>
Fix two issues in btintel_pcie_msix_tx_handle():
1. cr_tia is a device-controlled value from shared DMA memory
(data->ia.cr_tia[]) and is used to index txq->urbd0s[] without
a bounds check. An out-of-range value could cause an out-of-bounds
access when indexing txq->urbd0s[]. Add a bounds check before the
array access. When cr_tia is out of range, reset the ring consumer
pointer (data->ia.cr_tia[]) to cr_hia so the queue can recover on
the next interrupt.
2. The existing check on urbd0->tfd_index uses '>' instead of '>=',
allowing tfd_index == txq->count (32) to pass. This check guards
against a device-controlled value, so the comparison must reject
all out-of-range indices. Read tfd_index via READ_ONCE() to
ensure a single atomic read from DMA-coherent memory.
Fixes: c2b636b3f788 ("Bluetooth: btintel_pcie: Add support for PCIe transport")
Signed-off-by: ZhaoJinming <zhaojinming@uniontech.com>
---
drivers/bluetooth/btintel_pcie.c | 30 +++++++++++++++++++++++++++---
1 file changed, 27 insertions(+), 3 deletions(-)
diff --git a/drivers/bluetooth/btintel_pcie.c b/drivers/bluetooth/btintel_pcie.c
index fe50c5699e12ef3819577e0f0bd1b79d4340bd9e..c1fd5feb9f81bbd70fabd12b12eb4a1708f6a91f 100644
--- a/drivers/bluetooth/btintel_pcie.c
+++ b/drivers/bluetooth/btintel_pcie.c
@@ -1081,9 +1081,10 @@ static void btintel_pcie_msix_gp0_handler(struct btintel_pcie_data *data)
*/
static void btintel_pcie_msix_tx_handle(struct btintel_pcie_data *data)
{
- u16 cr_tia, cr_hia;
+ u16 cr_tia, cr_hia, tfd_index;
struct txq *txq;
struct urbd0 *urbd0;
+ struct hci_dev *hdev = data->hdev;
cr_tia = data->ia.cr_tia[BTINTEL_PCIE_TXQ_NUM];
cr_hia = data->ia.cr_hia[BTINTEL_PCIE_TXQ_NUM];
@@ -1094,13 +1095,36 @@ static void btintel_pcie_msix_tx_handle(struct btintel_pcie_data *data)
txq = &data->txq;
while (cr_tia != cr_hia) {
+ if (cr_tia >= txq->count) {
+ bt_dev_err(hdev, "TXQ: invalid cr_tia %u >= %u, contact device vendor",
+ cr_tia, txq->count);
+ /* Reset consumer pointer so the ring can
+ * recover on the next interrupt.
+ */
+ data->ia.cr_tia[BTINTEL_PCIE_TXQ_NUM] = cr_hia;
+ break;
+ }
+
data->tx_wait_done = true;
wake_up(&data->tx_wait_q);
urbd0 = &txq->urbd0s[cr_tia];
- if (urbd0->tfd_index > txq->count)
- return;
+ /* tfd_index is a bitfield in DMA-coherent memory;
+ * read the full word once with READ_ONCE to avoid
+ * TOCTOU race with the device.
+ */
+ tfd_index = READ_ONCE(*(const u32 *)urbd0) & 0xffff;
+
+ if (tfd_index >= txq->count) {
+ bt_dev_err(hdev, "TXQ: invalid tfd_index %u >= %u, contact device vendor",
+ tfd_index, txq->count);
+ /* Device provided invalid data. Leave cr_tia
+ * unchanged so the error remains detectable
+ * via repeated log messages, aiding debug.
+ */
+ break;
+ }
cr_tia = (cr_tia + 1) % txq->count;
data->ia.cr_tia[BTINTEL_PCIE_TXQ_NUM] = cr_tia;
--
2.51.0
next prev parent reply other threads:[~2026-08-20 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 9:17 [PATCH 0/3] Bluetooth: btintel_pcie: Fix array bounds of device-controlled indices ZhaoJinming
2026-08-20 9:17 ` [PATCH 1/3] Bluetooth: btintel_pcie: Fix off-by-one bounds checks in synchronous paths ZhaoJinming
2026-08-20 9:50 ` Bluetooth: btintel_pcie: Fix array bounds of device-controlled indices bluez.test.bot
2026-08-20 9:17 ` ZhaoJinming [this message]
2026-08-20 9:17 ` [PATCH 3/3] Bluetooth: btintel_pcie: Fix bounds checks in RX completion handler ZhaoJinming
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=20260820-btintel_pcie_bounds_fixes-v1-2-c9dcd1ac8bf6@uniontech.com \
--to=zhaojinming@uniontech.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
/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