From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Ran Menscher <ran.menscher@karambasecurity.com>
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: check the buffer size for some messages before parsing
Date: Thu, 10 Jan 2019 07:30:13 +0100 [thread overview]
Message-ID: <20190110063013.GD15047@kroah.com> (raw)
In-Reply-To: <20190110062917.GB15047@kroah.com>
On Thu, Jan 10, 2019 at 07:29:17AM +0100, Greg Kroah-Hartman wrote:
> The L2CAP_CONF_EFS and L2CAP_CONF_RFC messages can be sent from
> userspace so their structure sizes need to be checked before parsing
> them.
>
> Based on a patch from Ran Menscher.
Ran, can you verify if these two patches solve the problems you reported
or not?
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-10 6:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 6:28 [PATCH 1/2] Bluetooth: check message types in l2cap_get_conf_opt Greg Kroah-Hartman
2019-01-10 6:29 ` [PATCH 2/2] Bluetooth: check the buffer size for some messages before parsing Greg Kroah-Hartman
2019-01-10 6:30 ` Greg Kroah-Hartman [this message]
2019-01-18 9:37 ` Marcel Holtmann
2019-01-18 10:21 ` Greg Kroah-Hartman
2019-01-18 11:11 ` Marcel Holtmann
2019-01-18 12:44 ` Marcel Holtmann
2019-01-10 21:02 ` [PATCH 1/2] Bluetooth: check message types in l2cap_get_conf_opt Joe Perches
2019-01-11 5:32 ` Greg Kroah-Hartman
2019-01-18 9:35 ` Marcel Holtmann
2019-01-18 10:19 ` Greg Kroah-Hartman
2019-01-18 11:09 ` Marcel Holtmann
2019-01-18 12:08 ` Marcel Holtmann
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=20190110063013.GD15047@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=ran.menscher@karambasecurity.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).