All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fixes for 4.15-rc8
Date: Sat, 13 Jan 2018 21:30:16 +0100	[thread overview]
Message-ID: <20180113203016.GA11573@kroah.com> (raw)

The following changes since commit 30a7acd573899fd8b8ac39236eff6468b195ac7d:

  Linux 4.15-rc6 (2017-12-31 14:47:43 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ tags/char-misc-4.15-rc8

for you to fetch changes up to aa1f10e85b0ab53dee85d8e293c8159d18d293a8:

  mux: core: fix double get_device() (2018-01-09 14:19:41 +0100)

----------------------------------------------------------------
Char/Misc fixes for 4.15-rc8

Here are two bugfixes for some driver bugs for 4.15-rc8

The first is a bluetooth security bug that has been ignored by the
Bluetooth developers for months for no obvious reason at all, so I've
taken it through my tree.

The second is a simple double-free bug in the mux subsystem.

Both have been in linux-next for a while with no reported issues.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Ben Seri (1):
      Bluetooth: Prevent stack info leak from the EFS element.

Hans de Goede (1):
      mux: core: fix double get_device()

 drivers/mux/core.c         |  4 +++-
 net/bluetooth/l2cap_core.c | 20 +++++++++++---------
 2 files changed, 14 insertions(+), 10 deletions(-)

                 reply	other threads:[~2018-01-13 20:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180113203016.GA11573@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.