From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH v3 1/2] Bluetooth: L2CAP: Fix accepting channels with insufficient security
Date: Fri, 20 Nov 2026 10:48:15 -0500 [thread overview]
Message-ID: <20261120154816.1745952-1-luiz.dentz@gmail.com> (raw)
From: Mohammed Alquraini <mohammed.saad.alquraini@gmail.com>
When the link security changes, l2cap_security_cfm() doesn't check
that the result meets the security level required by the channels:
- If encryption completes it sets chan->sec_level to hcon->sec_level,
so a channel requiring a higher security level than the one the
link ended up with has its requirement lowered instead of being
refused.
- A channel in BT_CONNECT2 is accepted, or offered to the listener if
it uses BT_DEFER_SETUP, as long as the status is success and the
encryption key size is valid, e.g. if the peer disables encryption
while the channel waits for userspace to authorize it, the channel
is offered again and, once authorized, it is established over an
unencrypted link.
Fix this by treating encryption completing with a security level
below the one required by a channel as a downgrade: the security level
of the channel is no longer lowered and the channel is disconnected,
or refused with L2CAP_CR_SEC_BLOCK if it was pending, and by only
accepting a channel in BT_CONNECT2 if the link meets its security
level.
This means a channel requiring a security level that pairing can't
provide, e.g. BT_SECURITY_HIGH when the IO capability is
NoInputNoOutput, is now refused instead of being connected with the
security level the link ended up with.
AI assistance was used in finding and preparing this patch.
Fixes: f66dc81f44d9 ("Bluetooth: Add support for deferring L2CAP connection setup")
Signed-off-by: Mohammed Alquraini <mohammed.saad.alquraini@gmail.com>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
---
v3: Don't use l2cap_chan_check_security(), which may start
authentication or encryption, instead compare the security level
of the link with the one of the channel. Treat encryption
completing below the security level of the channel as a downgrade
and disconnect the channel instead of lowering its security level.
v2: Drop BT_SK_ACCEPTED and the changes to l2cap_sock_defer(), only check
l2cap_chan_check_security() in the BT_CONNECT2 branch of
l2cap_security_cfm(). The early accept is handled by patch 2/2.
---
net/bluetooth/l2cap_core.c | 42 ++++++++++++++++++++++++++++++++------
1 file changed, 36 insertions(+), 6 deletions(-)
diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
index 943effc86740..3fc0fecdbb5c 100644
--- a/net/bluetooth/l2cap_core.c
+++ b/net/bluetooth/l2cap_core.c
@@ -8095,11 +8095,19 @@ static inline void l2cap_check_encryption(struct l2cap_chan *chan, u8 encrypt)
}
}
+/* Check if the link meets the security level required by the channel */
+static bool l2cap_chan_sec_level_met(struct hci_conn *hcon,
+ struct l2cap_chan *chan)
+{
+ return chan->sec_level <= BT_SECURITY_LOW ||
+ hcon->sec_level >= chan->sec_level;
+}
+
static void l2cap_security_cfm(struct hci_conn *hcon, u8 status, u8 encrypt)
__must_hold(&hcon->hdev->lock)
{
struct l2cap_conn *conn = hcon->l2cap_data;
- struct l2cap_chan *chan;
+ struct l2cap_chan *chan, *tmp;
if (!conn)
return;
@@ -8108,7 +8116,9 @@ static void l2cap_security_cfm(struct hci_conn *hcon, u8 status, u8 encrypt)
mutex_lock(&conn->lock);
- list_for_each_entry(chan, &conn->chan_l, list) {
+ list_for_each_entry_safe(chan, tmp, &conn->chan_l, list) {
+ bool downgrade = false;
+
l2cap_chan_lock(chan);
lockdep_assert_held(&chan->conn->lock);
@@ -8116,14 +8126,32 @@ static void l2cap_security_cfm(struct hci_conn *hcon, u8 status, u8 encrypt)
BT_DBG("chan %p scid 0x%4.4x state %s", chan, chan->scid,
state_to_string(chan->state));
- if (!status && encrypt)
- chan->sec_level = hcon->sec_level;
+ if (!status && encrypt) {
+ /* Encryption completing with a security level below
+ * the one the channel requires is a downgrade, don't
+ * lower the requirement of the channel to match it.
+ */
+ if (!l2cap_chan_sec_level_met(hcon, chan))
+ downgrade = true;
+ else
+ chan->sec_level = hcon->sec_level;
+ }
if (!__l2cap_no_conn_pending(chan)) {
l2cap_chan_unlock(chan);
continue;
}
+ if (downgrade && (chan->state == BT_CONNECTED ||
+ chan->state == BT_CONFIG)) {
+ /* Fixed channels are removed from the list */
+ l2cap_chan_hold(chan);
+ __l2cap_chan_close(chan, ECONNREFUSED);
+ l2cap_chan_unlock(chan);
+ l2cap_chan_put(chan);
+ continue;
+ }
+
if (!status && (chan->state == BT_CONNECTED ||
chan->state == BT_CONFIG)) {
chan->ops->resume(chan);
@@ -8133,7 +8161,8 @@ static void l2cap_security_cfm(struct hci_conn *hcon, u8 status, u8 encrypt)
}
if (chan->state == BT_CONNECT) {
- if (!status && l2cap_check_enc_key_size(hcon, chan))
+ if (!status && !downgrade &&
+ l2cap_check_enc_key_size(hcon, chan))
l2cap_start_connection(chan);
else
__set_chan_timer(chan, L2CAP_DISC_TIMEOUT);
@@ -8143,7 +8172,8 @@ static void l2cap_security_cfm(struct hci_conn *hcon, u8 status, u8 encrypt)
struct l2cap_conn_rsp rsp;
__u16 res, stat;
- if (!status && l2cap_check_enc_key_size(hcon, chan)) {
+ if (!status && l2cap_check_enc_key_size(hcon, chan) &&
+ l2cap_chan_sec_level_met(hcon, chan)) {
if (test_bit(FLAG_DEFER_SETUP, &chan->flags)) {
res = L2CAP_CR_PEND;
stat = L2CAP_CS_AUTHOR_PEND;
--
2.56.0
next reply other threads:[~2026-11-20 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 15:48 Luiz Augusto von Dentz [this message]
2026-11-20 15:48 ` [PATCH v3 2/2] Bluetooth: L2CAP: Don't offer deferred channels before security is met Luiz Augusto von Dentz
2026-11-20 21:37 ` [v3,1/2] Bluetooth: L2CAP: Fix accepting channels with insufficient security bluez.test.bot
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=20261120154816.1745952-1-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.