From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: security bump to the latest 2.26 branch
Date: Fri, 08 Dec 2017 14:33:41 +0100 [thread overview]
Message-ID: <87efo5z6mi.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <4f77d70e07b0ed078d79e0358ec3ff3d49ccb093.1512717176.git.baruch@tkos.co.il> (Baruch Siach's message of "Fri, 8 Dec 2017 09:12:56 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> List of fixes from the 2.26 branch NEWS files:
> CVE-2017-15670: The glob function, when invoked with GLOB_TILDE,
> suffered from a one-byte overflow during ~ operator processing (either
> on the stack or the heap, depending on the length of the user name).
> Reported by Tim R?hsen.
> CVE-2017-15671: The glob function, when invoked with GLOB_TILDE,
> would sometimes fail to free memory allocated during ~ operator
> processing, leading to a memory leak and, potentially, to a denial
> of service.
> CVE-2017-15804: The glob function, when invoked with GLOB_TILDE and
> without GLOB_NOESCAPE, could write past the end of a buffer while
> unescaping user names. Reported by Tim R?hsen.
> CVE-2017-17426: The malloc function, when called with an object size near
> the value SIZE_MAX, would return a pointer to a buffer which is too small,
> instead of NULL. This was a regression introduced with the new malloc
> thread cache in glibc 2.26. Reported by Iain Buclaw.
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-12-08 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 7:12 [Buildroot] [PATCH] glibc: security bump to the latest 2.26 branch Baruch Siach
2017-12-08 13:33 ` Peter Korsgaard [this message]
2017-12-27 11:44 ` Peter Korsgaard
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=87efo5z6mi.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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