From: Szymon Janc <szymon.janc@tieto.com>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Fix BR/EDR-only address checks for remote OOB data
Date: Mon, 17 Nov 2014 18:37:14 +0100 [thread overview]
Message-ID: <4362075.XVFnp0kduk@leonov> (raw)
In-Reply-To: <1416242965-29207-1-git-send-email-johan.hedberg@gmail.com>
Hi Johan,
On Monday 17 of November 2014 18:49:25 Johan Hedberg wrote:
> From: Johan Hedberg <johan.hedberg@intel.com>
>
> For now the mgmt commands dealing with remote OOB data are strictly
> BR/EDR-only. This patch fixes missing checks for the passed address type
> so that any non-BR/EDR value triggers the appropriate error response.
>
> Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
> ---
> net/bluetooth/mgmt.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/net/bluetooth/mgmt.c b/net/bluetooth/mgmt.c
> index b84c0923ec62..aaaa605f48b0 100644
> --- a/net/bluetooth/mgmt.c
> +++ b/net/bluetooth/mgmt.c
> @@ -3589,6 +3589,13 @@ static int add_remote_oob_data(struct sock *sk,
> struct hci_dev *hdev, struct mgmt_cp_add_remote_oob_data *cp = data;
> u8 status;
>
> + if (cp->addr.type != BDADDR_BREDR) {
> + err = cmd_status(sk, hdev->id,
> + MGMT_OP_ADD_REMOTE_OOB_DATA,
> + MGMT_STATUS_INVALID_PARAMS);
> + goto unlock;
> + }
This should generate command complete event.
(it looks like there is also similar bug in 'else' case in the code)
> +
> err = hci_add_remote_oob_data(hdev, &cp->addr.bdaddr,
> cp->hash, cp->randomizer);
> if (err < 0)
> @@ -3602,6 +3609,13 @@ static int add_remote_oob_data(struct sock *sk,
> struct hci_dev *hdev, struct mgmt_cp_add_remote_oob_ext_data *cp = data;
> u8 status;
>
> + if (cp->addr.type != BDADDR_BREDR) {
> + err = cmd_status(sk, hdev->id,
> + MGMT_OP_ADD_REMOTE_OOB_DATA,
> + MGMT_STATUS_INVALID_PARAMS);
> + goto unlock;
> + }
Same here.
> +
> err = hci_add_remote_oob_ext_data(hdev, &cp->addr.bdaddr,
> cp->hash192,
> cp->randomizer192,
> @@ -3620,6 +3634,7 @@ static int add_remote_oob_data(struct sock *sk, struct
> hci_dev *hdev, MGMT_STATUS_INVALID_PARAMS);
> }
>
> +unlock:
> hci_dev_unlock(hdev);
> return err;
> }
> @@ -3633,6 +3648,10 @@ static int remove_remote_oob_data(struct sock *sk,
> struct hci_dev *hdev,
>
> BT_DBG("%s", hdev->name);
>
> + if (cp->addr.type != BDADDR_BREDR)
> + return cmd_status(sk, hdev->id, MGMT_OP_REMOVE_REMOTE_OOB_DATA,
> + MGMT_STATUS_INVALID_PARAMS);
> +
And here.
> hci_dev_lock(hdev);
>
> if (!bacmp(&cp->addr.bdaddr, BDADDR_ANY)) {
--
BR
Szymon Janc
next prev parent reply other threads:[~2014-11-17 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 16:49 [PATCH] Bluetooth: Fix BR/EDR-only address checks for remote OOB data Johan Hedberg
2014-11-17 17:37 ` Szymon Janc [this message]
2014-11-17 18:51 ` Johan Hedberg
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=4362075.XVFnp0kduk@leonov \
--to=szymon.janc@tieto.com \
--cc=johan.hedberg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox