From: Tedd Ho-Jeong An <tedd.an@linux.intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM
Date: Tue, 01 Nov 2022 11:57:06 -0700 [thread overview]
Message-ID: <012893abec97796db9f187a9d5c42477b5ebc54a.camel@linux.intel.com> (raw)
In-Reply-To: <20221031231033.2718204-1-luiz.dentz@gmail.com>
Hi Luiz,
On Mon, 2022-10-31 at 16:10 -0700, Luiz Augusto von Dentz wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> The Bluetooth spec states that the valid range for SPSM is from
> 0x0001-0x00ff so it is invalid to accept values outside of this range:
>
> BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 3, Part A
> page 1059:
> Table 4.15: L2CAP_LE_CREDIT_BASED_CONNECTION_REQ SPSM ranges
>
> CVE: CVE-2022-42896
> CC: stable@vger.kernel.org
> Reported-by: Tamás Koczka <poprdi@google.com>
Reviewed-by: Tedd Ho-Jeong An <tedd.an@intel.com>
> Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> ---
> net/bluetooth/l2cap_core.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index ef725ed41303..2978a34ea33f 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -5813,6 +5813,19 @@ static int l2cap_le_connect_req(struct l2cap_conn *conn,
> BT_DBG("psm 0x%2.2x scid 0x%4.4x mtu %u mps %u", __le16_to_cpu(psm),
> scid, mtu, mps);
>
> + /* BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 3, Part A
> + * page 1059:
> + *
> + * Valid range: 0x0001-0x00ff
> + *
> + * Table 4.15: L2CAP_LE_CREDIT_BASED_CONNECTION_REQ SPSM ranges
> + */
> + if (!psm || __le16_to_cpu(psm) > L2CAP_PSM_LE_DYN_END) {
> + result = L2CAP_CR_LE_BAD_PSM;
> + chan = NULL;
> + goto response;
> + }
> +
> /* Check if we have socket listening on psm */
> pchan = l2cap_global_chan_by_psm(BT_LISTEN, psm, &conn->hcon->src,
> &conn->hcon->dst, LE_LINK);
> @@ -6001,6 +6014,18 @@ static inline int l2cap_ecred_conn_req(struct l2cap_conn *conn,
>
> psm = req->psm;
>
> + /* BLUETOOTH CORE SPECIFICATION Version 5.3 | Vol 3, Part A
> + * page 1059:
> + *
> + * Valid range: 0x0001-0x00ff
> + *
> + * Table 4.15: L2CAP_LE_CREDIT_BASED_CONNECTION_REQ SPSM ranges
> + */
> + if (!psm || __le16_to_cpu(psm) > L2CAP_PSM_LE_DYN_END) {
> + result = L2CAP_CR_LE_BAD_PSM;
> + goto response;
> + }
> +
> BT_DBG("psm 0x%2.2x mtu %u mps %u", __le16_to_cpu(psm), mtu, mps);
>
> memset(&pdu, 0, sizeof(pdu));
Regards,
Tedd
next prev parent reply other threads:[~2022-11-01 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 23:10 [PATCH 1/2] Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM Luiz Augusto von Dentz
2022-10-31 23:10 ` [PATCH 2/2] Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm Luiz Augusto von Dentz
2022-11-01 0:13 ` [1/2] Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM bluez.test.bot
2022-11-01 18:57 ` Tedd Ho-Jeong An [this message]
2022-11-01 20:50 ` [PATCH 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=012893abec97796db9f187a9d5c42477b5ebc54a.camel@linux.intel.com \
--to=tedd.an@linux.intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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