From: "Charles (Chas) Williams" <3chas3@gmail.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH -stable] multiple backports requested
Date: Fri, 13 Nov 2015 15:13:11 -0500 [thread overview]
Message-ID: <1447445591.2645.17.camel@gmail.com> (raw)
Dave, could you please add the following backports?
For the 3.14.y stable queue:
commit 77751427a1ff25b27d47a4c36b12c3c8667855ac
ipv6: addrconf: validate new MTU before applying it
This addresses CVE-2015-0272
commit 74e98eb085889b0d2d4908f59f6e00026063014f
RDS: verify the underlying transport exists before creating a connection
This addresses CVE-2015-6937
For the 4.1.y stable queue:
commit 74e98eb085889b0d2d4908f59f6e00026063014f
RDS: verify the underlying transport exists before creating a connection
This addresses CVE-2015-6937
Thanks!
next reply other threads:[~2015-11-13 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 20:13 Charles (Chas) Williams [this message]
2015-11-13 21:10 ` [PATCH -stable] multiple backports requested David Miller
2015-11-14 11:34 ` Charles (Chas) Williams
2015-11-14 17:24 ` David Miller
2015-11-15 11:19 ` Charles (Chas) Williams
2015-11-15 17:46 ` David Miller
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=1447445591.2645.17.camel@gmail.com \
--to=3chas3@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@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).