From: Ben Hutchings <ben@decadent.org.uk>
To: stable <stable@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>
Subject: [stable] [media] dvb-usb-v2: avoid use-after-free
Date: Tue, 18 Apr 2017 03:07:17 +0100 [thread overview]
Message-ID: <1492481237.2409.127.camel@decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 317 bytes --]
Please apply this to all stable branches back to 3.7:
commit 005145378c9ad7575a01b6ce1ba118fb427f583a
Author: Arnd Bergmann <arnd@arndb.de>
Date: Thu Feb 2 12:36:01 2017 -0200
[media] dvb-usb-v2: avoid use-after-free
Ben.
--
Ben Hutchings
The world is coming to an end. Please log off.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2017-04-18 2:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 2:07 Ben Hutchings [this message]
2017-04-19 11:53 ` [stable] [media] dvb-usb-v2: avoid use-after-free Greg KH
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=1492481237.2409.127.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=arnd@arndb.de \
--cc=mchehab@s-opensource.com \
--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).