All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/glibc: bump version for additional post-2.30 security fixes
Date: Tue, 12 May 2020 13:58:07 +0200	[thread overview]
Message-ID: <87lflxl60g.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200512085324.22685-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 12 May 2020 10:53:23 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > Fixes the following security vulnerabilities:
 > CVE-2020-10029: Trigonometric functions on x86 targets suffered from stack
 >   corruption when they were passed a pseudo-zero argument.  Reported by Guido
 >   Vranken / ForAllSecure Mayhem.

 > CVE-2020-1751: A defect in the PowerPC backtrace function could cause an
 >   out-of-bounds write when executed in a signal frame context.

 > CVE-2020-1752: A use-after-free vulnerability in the glob function when
 >   expanding ~user has been fixed.

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed to 2020.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2020-05-12 11:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  8:53 [Buildroot] [PATCH v2 1/2] package/glibc: bump version for additional post-2.30 security fixes Peter Korsgaard
2020-05-12  8:53 ` [Buildroot] [PATCH v2 2/2] package/localedef: bump version to stay in sync with glibc Peter Korsgaard
2020-05-12 10:27   ` Peter Korsgaard
2020-05-12 11:58   ` Peter Korsgaard
2020-05-12 10:27 ` [Buildroot] [PATCH v2 1/2] package/glibc: bump version for additional post-2.30 security fixes Peter Korsgaard
2020-05-12 11:58 ` Peter Korsgaard [this message]

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=87lflxl60g.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 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.