From: Dan Carpenter <dan.carpenter@oracle.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Tomas Bortoli <tomasbortoli@gmail.com>
Subject: Re: [Patch net v2 2/3] bluetooth: validate HCI_EV_LE_META packet carefully
Date: Thu, 4 Apr 2019 11:34:49 +0300 [thread overview]
Message-ID: <20190404083449.GL32613@kadam> (raw)
In-Reply-To: <20190403230835.1174-3-xiyou.wangcong@gmail.com>
On Wed, Apr 03, 2019 at 04:08:34PM -0700, Cong Wang wrote:
> static void hci_le_ext_adv_report_evt(struct hci_dev *hdev, struct sk_buff *skb)
> {
> - u8 num_reports = skb->data[0];
> - void *ptr = &skb->data[1];
> + unsigned int len;
> + u8 num_reports;
> +
> + if (unlikely(!pskb_may_pull(skb, 1)))
> + return;
> + num_reports = skb->data[0];
> + len = 1;
>
> hci_dev_lock(hdev);
>
> while (num_reports--) {
> - struct hci_ev_le_ext_adv_report *ev = ptr;
> + struct hci_ev_le_ext_adv_report *ev;
> u8 legacy_evt_type;
> u16 evt_type;
> + u8 ev_len;
> +
> + if (unlikely(!pskb_may_pull(skb, len + sizeof(*ev))))
> + break;
> + ev = (void *)skb->data + len;
> + ev_len = ev->length + 1;
The "+ 1" is a bug. It was discussed in a different thread. Jaganath
says he has sent a patch to fix it already.
Probably it worked in testing because the num_reports was always 1, but
now when we add this condition with the "+ 1" bug at the start of the
loop the the the num_reports == 1 case will be broken as well.
Tomas and I should get Reported-by tags for parts of this patch.
> + if (unlikely(!pskb_may_pull(skb, len + sizeof(*ev) + ev_len)))
> + break;
> + ev = (void *)skb->data + len;
>
> evt_type = __le16_to_cpu(ev->evt_type);
> legacy_evt_type = ext_evt_type_to_legacy(evt_type);
> @@ -5601,7 +5645,7 @@ static void hci_le_ext_adv_report_evt(struct hci_dev *hdev, struct sk_buff *skb)
> ev->data, ev->length);
> }
>
> - ptr += sizeof(*ev) + ev->length + 1;
> + len += sizeof(*ev) + ev_len;
> }
>
> hci_dev_unlock(hdev);
regards,
dan carpenter
next prev parent reply other threads:[~2019-04-04 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 23:08 [Patch net v2 0/3] bluetooth: validate packet boundary carefully Cong Wang
2019-04-03 23:08 ` [Patch net v2 1/3] bluetooth: validate HCI_EVENT_PKT packet carefully Cong Wang
2019-04-23 19:42 ` Marcel Holtmann
2019-04-24 1:36 ` Cong Wang
2019-04-03 23:08 ` [Patch net v2 2/3] bluetooth: validate HCI_EV_LE_META " Cong Wang
2019-04-04 8:34 ` Dan Carpenter [this message]
2019-04-05 17:26 ` Cong Wang
2019-04-05 20:09 ` Dan Carpenter
2019-04-03 23:08 ` [Patch net v2 3/3] bluetooth: validate HCI_EV_CMD_COMPLETE " Cong Wang
-- strict thread matches above, loose matches on Subject: below --
2019-03-21 6:12 [Patch net v2 0/3] bluetooth: validate packet boundary carefully Cong Wang
2019-03-21 6:12 ` [Patch net v2 2/3] bluetooth: validate HCI_EV_LE_META packet carefully Cong Wang
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=20190404083449.GL32613@kadam \
--to=dan.carpenter@oracle.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=tomasbortoli@gmail.com \
--cc=xiyou.wangcong@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;
as well as URLs for NNTP newsgroup(s).