From: Armin Kuster <akuster808@gmail.com>
To: akuster@mvista.com, openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Several Glibc security fixes
Date: Wed, 22 Nov 2017 19:52:14 -0800 [thread overview]
Message-ID: <1511409137-30823-1-git-send-email-akuster808@gmail.com> (raw)
The pending 2.27 update does not need these. Only apply if that update is delayed too long.
affects glibc < 2.27
This will hit stable/Rocko-next shortly
Armin Kuster (3):
glibc: Security fix CVE-2017-15670
glibc: Security fix CVE-2017-15671
glibc: Security fix for CVE-2017-15804
meta/recipes-core/glibc/glibc/CVE-2017-15670.patch | 61 ++++++
meta/recipes-core/glibc/glibc/CVE-2017-15671.patch | 215 +++++++++++++++++++++
meta/recipes-core/glibc/glibc/CVE-2017-15804.patch | 111 +++++++++++
meta/recipes-core/glibc/glibc_2.26.bb | 3 +
4 files changed, 390 insertions(+)
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2017-15670.patch
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2017-15671.patch
create mode 100644 meta/recipes-core/glibc/glibc/CVE-2017-15804.patch
--
2.7.4
next reply other threads:[~2017-11-23 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 3:52 Armin Kuster [this message]
2017-11-23 3:52 ` [PATCH 1/3] glibc: Security fix CVE-2017-15670 Armin Kuster
2017-11-23 3:52 ` [PATCH 2/3] glibc: Security fix CVE-2017-15671 Armin Kuster
2017-11-23 3:52 ` [PATCH 3/3] glibc: Security fix for CVE-2017-15804 Armin Kuster
2017-11-23 4:03 ` ✗ patchtest: failure for Several Glibc security fixes Patchwork
2017-11-23 12:00 ` [PATCH 0/3] " Burton, Ross
2017-11-23 16:16 ` akuster808
2017-11-27 1:47 ` Khem Raj
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=1511409137-30823-1-git-send-email-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=akuster@mvista.com \
--cc=openembedded-core@lists.openembedded.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