linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linma <linma@zju.edu.cn>, "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>,
	"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Hao Xiong <mart1n@zju.edu.cn>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH v2] Bluetooth: fix the erroneous flush_work() order
Date: Tue, 8 Jun 2021 10:32:02 +0200	[thread overview]
Message-ID: <YL8rAlo56DT9Ok0B@kroah.com> (raw)
In-Reply-To: <YL73vTBtgWkaup+A@eldamar.lan>

On Tue, Jun 08, 2021 at 06:53:17AM +0200, Salvatore Bonaccorso wrote:
> Hi Greg,
> 
> On Thu, May 27, 2021 at 10:14:59PM +0200, Marcel Holtmann wrote:
> > Hi Greg,
> > 
> > > In the cleanup routine for failed initialization of HCI device,
> > > the flush_work(&hdev->rx_work) need to be finished before the
> > > flush_work(&hdev->cmd_work). Otherwise, the hci_rx_work() can
> > > possibly invoke new cmd_work and cause a bug, like double free,
> > > in late processings.
> > > 
> > > This was assigned CVE-2021-3564.
> > > 
> > > This patch reorder the flush_work() to fix this bug.
> > > 
> > > Cc: Marcel Holtmann <marcel@holtmann.org>
> > > Cc: Johan Hedberg <johan.hedberg@gmail.com>
> > > Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
> > > Cc: "David S. Miller" <davem@davemloft.net>
> > > Cc: Jakub Kicinski <kuba@kernel.org>
> > > Cc: linux-bluetooth@vger.kernel.org
> > > Cc: netdev@vger.kernel.org
> > > Cc: linux-kernel@vger.kernel.org
> > > Signed-off-by: Lin Ma <linma@zju.edu.cn>
> > > Signed-off-by: Hao Xiong <mart1n@zju.edu.cn>
> > > Cc: stable <stable@vger.kernel.org>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > ---
> > > net/bluetooth/hci_core.c | 7 ++++++-
> > > 1 file changed, 6 insertions(+), 1 deletion(-)
> > 
> > patch has been applied to bluetooth-stable tree.
> 
> Can you queue this one as well for the stable series? It is
> 6a137caec23aeb9e036cdfd8a46dd8a366460e5d commit upstream and in
> 5.13-rc5.

It's now queued up, thanks.

greg k-h

      reply	other threads:[~2021-06-08  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 12:39 [PATCH v2] Bluetooth: fix the erroneous flush_work() order Greg Kroah-Hartman
2021-05-25 13:36 ` [v2] " bluez.test.bot
2021-05-25 14:21   ` Greg KH
2021-05-25 18:16     ` Luiz Augusto von Dentz
2021-05-27 20:14 ` [PATCH v2] " Marcel Holtmann
2021-06-08  4:53   ` Salvatore Bonaccorso
2021-06-08  8:32     ` Greg Kroah-Hartman [this message]

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=YL8rAlo56DT9Ok0B@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=carnil@debian.org \
    --cc=davem@davemloft.net \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linma@zju.edu.cn \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=mart1n@zju.edu.cn \
    --cc=netdev@vger.kernel.org \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).