From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ v1 2/2] emulator/btdev: Check valid range of CE Length
Date: Wed, 2 Sep 2026 11:09:51 -0400 [thread overview]
Message-ID: <20260902150951.1583184-2-luiz.dentz@gmail.com> (raw)
In-Reply-To: <20260902150951.1583184-1-luiz.dentz@gmail.com>
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
The connection event length recommended in requests by a Peripheral has
a valid range of 0x0001 to 0x7CFF (Time = N * 125 us, Time Range:
0.125 ms to 3.999875 s), so reject LE Connection Rate Request and LE Set
Default Rate Parameters with values outside of it.
---
emulator/btdev.c | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/emulator/btdev.c b/emulator/btdev.c
index a53bd82526d9..bc573c3a2370 100644
--- a/emulator/btdev.c
+++ b/emulator/btdev.c
@@ -7963,6 +7963,27 @@ static void set_le_60_commands(struct btdev *btdev)
btdev->cmds = cmd_le_6_0;
}
+/* Connection event length recommended in requests by a Peripheral:
+ * Range: 0x0001 to 0x7CFF, Time = N * 125 us
+ * Time Range: 0.125 ms to 3.999875 s
+ */
+#define BT_HCI_CE_LEN_MIN 0x0001
+#define BT_HCI_CE_LEN_MAX 0x7cff
+
+static bool valid_ce_len(uint16_t min_ce_len, uint16_t max_ce_len)
+{
+ uint16_t min = le16_to_cpu(min_ce_len);
+ uint16_t max = le16_to_cpu(max_ce_len);
+
+ if (min < BT_HCI_CE_LEN_MIN || min > BT_HCI_CE_LEN_MAX)
+ return false;
+
+ if (max < BT_HCI_CE_LEN_MIN || max > BT_HCI_CE_LEN_MAX)
+ return false;
+
+ return min <= max;
+}
+
static int cmd_le_conn_rate(struct btdev *dev, const void *data, uint8_t len)
{
const struct bt_hci_cmd_le_conn_rate *cmd = data;
@@ -7974,6 +7995,8 @@ static int cmd_le_conn_rate(struct btdev *dev, const void *data, uint8_t len)
UINT_TO_PTR(le16_to_cpu(cmd->handle)));
if (!conn)
status = BT_HCI_ERR_UNKNOWN_CONN_ID;
+ else if (!valid_ce_len(cmd->min_ce_len, cmd->max_ce_len))
+ status = BT_HCI_ERR_INVALID_PARAMETERS;
cmd_status(dev, status, BT_HCI_CMD_LE_CONN_RATE);
@@ -7999,8 +8022,12 @@ static int cmd_le_conn_rate(struct btdev *dev, const void *data, uint8_t len)
static int cmd_le_set_def_rate(struct btdev *dev, const void *data, uint8_t len)
{
+ const struct bt_hci_cmd_le_set_def_rate *cmd = data;
uint8_t status = BT_HCI_ERR_SUCCESS;
+ if (!valid_ce_len(cmd->min_ce_len, cmd->max_ce_len))
+ status = BT_HCI_ERR_INVALID_PARAMETERS;
+
cmd_complete(dev, BT_HCI_CMD_LE_SET_DEF_RATE, &status, sizeof(status));
return 0;
--
2.54.0
next prev parent reply other threads:[~2026-09-02 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 15:09 [PATCH BlueZ v1 1/2] monitor: Check valid range of CE Length Luiz Augusto von Dentz
2026-09-02 15:09 ` Luiz Augusto von Dentz [this message]
2026-09-02 18:09 ` [BlueZ,v1,1/2] " bluez.test.bot
2026-09-10 15:30 ` [PATCH BlueZ v1 1/2] " 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=20260902150951.1583184-2-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.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.