From: Marcus Cooper <marcus.cooper@axis.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/3] systemd: Fixes Security fix CVE-2018-16864 - CVE-2018-16866
Date: Mon, 28 Jan 2019 12:17:29 +0100 [thread overview]
Message-ID: <20190128111732.16387-1-marcusc@axis.com> (raw)
Changed in v2:
- Added CVE tag, Upstream-Status tag and Sign-off-by tags.
- removed the verification of the entry length in the header
- squashed CVE-2018-16865 patches into one
- CVE-2018-16866 patch now taken from systemd-stable and includes
an additional heap buffer overflow fix.
Marcus Cooper (3):
systemd: Security fix CVE-2018-16864
systemd: Security fix CVE-2018-16865
systemd: Security fix CVE-2018-16866
...-not-store-the-iovec-entry-for-process-co.patch | 208 +++++++++++++++++++++
...rnald-set-a-limit-on-the-number-of-fields.patch | 139 ++++++++++++++
...nal-fix-out-of-bounds-read-CVE-2018-16866.patch | 49 +++++
meta/recipes-core/systemd/systemd_239.bb | 3 +
4 files changed, 399 insertions(+)
create mode 100644 meta/recipes-core/systemd/systemd/0024-journald-do-not-store-the-iovec-entry-for-process-co.patch
create mode 100644 meta/recipes-core/systemd/systemd/0025-journald-set-a-limit-on-the-number-of-fields.patch
create mode 100644 meta/recipes-core/systemd/systemd/0026-journal-fix-out-of-bounds-read-CVE-2018-16866.patch
--
2.11.0
next reply other threads:[~2019-01-28 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 11:17 Marcus Cooper [this message]
2019-01-28 11:17 ` [PATCH v2 1/3] systemd: Security fix CVE-2018-16864 Marcus Cooper
2019-01-28 11:17 ` [PATCH v2 2/3] systemd: Security fix CVE-2018-16865 Marcus Cooper
2019-01-28 11:17 ` [PATCH v2 3/3] systemd: Security fix CVE-2018-16866 Marcus Cooper
2019-01-28 11:20 ` [PATCH v2 0/3] systemd: Fixes Security fix CVE-2018-16864 - CVE-2018-16866 Alexander Kanavin
2019-01-28 16:58 ` Khem Raj
2019-01-28 17:37 ` akuster808
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=20190128111732.16387-1-marcusc@axis.com \
--to=marcus.cooper@axis.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 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.