From: joeyli <jlee@suse.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: hci_event: Ignore NULL link key
Date: Mon, 17 Jul 2023 13:38:03 +0800 [thread overview]
Message-ID: <20230717053803.GN5866@linux-l9pv.suse> (raw)
In-Reply-To: <CABBYNZJ46Lt-Y4OjT7AqXczaGyGoRTzEA0gpG4Z+91GugHwsNw@mail.gmail.com>
Hi Luiz Augusto von Dentz,
First, thanks for your review!
On Fri, Jul 14, 2023 at 11:44:28AM -0700, Luiz Augusto von Dentz wrote:
> Hi Chun-Yi,
>
> On Fri, Jul 14, 2023 at 9:14 AM Lee, Chun-Yi <joeyli.kernel@gmail.com> wrote:
> >
> > This change is used to relieve CVE-2020-26555. The description of the
> > CVE:
> >
> > Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification
> > 1.0B through 5.2 may permit an unauthenticated nearby device to spoof
> > the BD_ADDR of the peer device to complete pairing without knowledge
> > of the PIN. [1]
> >
> > The detail of this attack is in IEEE paper:
> > BlueMirror: Reflections on Bluetooth Pairing and Provisioning Protocols
> > [2]
> >
> > It's a reflection attack. Base on the paper, attacker can induce the
> > attacked target to generate null link key (zero key) without PIN code.
> >
> > We can ignore null link key in the handler of "Link Key Notification
> > event" to relieve the attack. A similar implementation also shows in
> > btstack project. [3]
> >
> > Closes: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26555 [1]
> > Closes: https://ieeexplore.ieee.org/abstract/document/9474325/authors#authors [2]
> > Closes: https://github.com/bluekitchen/btstack/blob/master/src/hci.c#L3722 [3]
>
> Shouldn't the last 2 be using Link: instead?
>
Sorry for I confused Link: with Closes:. I will change all of them to Link: tag
> > Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
> > ---
> > net/bluetooth/hci_event.c | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> > index 95816a938cea..e81b8d6c13ba 100644
> > --- a/net/bluetooth/hci_event.c
> > +++ b/net/bluetooth/hci_event.c
> > @@ -4684,6 +4684,12 @@ static void hci_link_key_notify_evt(struct hci_dev *hdev, void *data,
> > bool persistent;
> > u8 pin_len = 0;
> >
> > + /* Ignore NULL link key against CVE-2020-26555 */
> > + if (!memcmp(ev->link_key, ZERO_KEY, HCI_LINK_KEY_SIZE)) {
> > + BT_DBG("Ignore NULL link key (ZERO KEY) for %pMR", &ev->bdaddr);
>
> Please use bt_dev_dbg instead.
>
I see! I will use bt_dev_dbg.
> > + return;
> > + }
> > +
> > bt_dev_dbg(hdev, "");
> >
> > hci_dev_lock(hdev);
> > --
> > 2.35.3
> >
Thanks a lot!
Joey Lee
next prev parent reply other threads:[~2023-07-17 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 16:12 [PATCH] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-07-14 18:44 ` Luiz Augusto von Dentz
2023-07-17 5:38 ` joeyli [this message]
[not found] ` <8eeb958e-d947-2f6d-5942-d30746cf1268@web.de>
2023-07-17 5:51 ` [PATCH] Bluetooth: hci_event: Ignore NULL link key in hci_link_key_notify_evt() joeyli
[not found] ` <7cae670e-b7c5-470b-536b-ab03513cd0a3@web.de>
2023-07-17 10:23 ` joeyli
2023-07-17 11:25 ` Dan Carpenter
2023-07-17 15:48 ` joeyli
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=20230717053803.GN5866@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=davem@davemloft.net \
--cc=joeyli.kernel@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.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