From: Greg KH <gregkh@linuxfoundation•org>
To: Peilin Ye <yepeilin.cs@gmail•com>
Cc: Marcel Holtmann <marcel@holtmann•org>,
Johan Hedberg <johan.hedberg@gmail•com>,
"David S . Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
Russell King <linux@armlinux•org.uk>,
linux-bluetooth@vger•kernel.org, netdev@vger•kernel.org,
syzkaller-bugs@googlegroups•com,
linux-kernel-mentees@lists•linuxfoundation.org,
linux-kernel@vger•kernel.org
Subject: Re: [Linux-kernel-mentees] [PATCH v2] net/bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt()
Date: Fri, 10 Jul 2020 12:43:06 +0200 [thread overview]
Message-ID: <20200710104306.GA1229536@kroah.com> (raw)
In-Reply-To: <20200709130224.214204-1-yepeilin.cs@gmail.com>
On Thu, Jul 09, 2020 at 09:02:24AM -0400, Peilin Ye wrote:
> Check upon `num_rsp` is insufficient. A malformed event packet with a
> large `num_rsp` number makes hci_extended_inquiry_result_evt() go out
> of bounds. Fix it.
>
> This patch fixes the following syzbot bug:
>
> https://syzkaller.appspot.com/bug?id=4bf11aa05c4ca51ce0df86e500fce486552dc8d2
>
> Reported-by: syzbot+d8489a79b781849b9c46@syzkaller•appspotmail.com
> Signed-off-by: Peilin Ye <yepeilin.cs@gmail•com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Bluetooth maintainers, can you also add a cc: stable on this so it gets
picked up properly there?
thanks,
greg k-h
next prev parent reply other threads:[~2020-07-10 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 5:18 [Linux-kernel-mentees] [PATCH] net/bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt() Peilin Ye
2020-07-09 13:02 ` [Linux-kernel-mentees] [PATCH v2] " Peilin Ye
2020-07-10 10:43 ` Greg KH [this message]
2020-07-10 16:09 ` [Linux-kernel-mentees] [PATCH v3] " Peilin Ye
2020-07-10 17:08 ` Marcel Holtmann
2021-07-01 15:39 ` maybe similar bug exists for HCI_EV_INQUIRY_RESULT* like [Linux-kernel-mentees] [PATCH v2] net/bluetooth: " Alexander Larkin
2021-07-01 21:06 ` Peilin Ye
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=20200710104306.GA1229536@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=johan.hedberg@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-kernel-mentees@lists$(echo .)linuxfoundation.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@armlinux$(echo .)org.uk \
--cc=marcel@holtmann$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=yepeilin.cs@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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