public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Move NEWS entry for CVE-2020-1751 to the 2.31 section
Date: Fri, 31 Jul 2020 11:00:00 +0000 (GMT)	[thread overview]
Message-ID: <20200731110000.557A73858D35@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7f1a08cff82255cd4252a2c75fd65b80a6a170bf

commit 7f1a08cff82255cd4252a2c75fd65b80a6a170bf
Author: Florian Weimer <fweimer@redhat.com>
Date:   Fri Jul 31 12:07:06 2020 +0200

    Move NEWS entry for CVE-2020-1751 to the 2.31 section
    
    It was fixed in commit d93769405996dfc11d216ddbe415946617b5a494
    ("Fix array overflow in backtrace on PowerPC (bug 25423)"), which
    went into glibc 2.31.
    
    Reviewed-by: Carlos O'Donell <carlos@redhat.com>

Diff:
---
 NEWS | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/NEWS b/NEWS
index 7fb167e650..85f91b3ecb 100644
--- a/NEWS
+++ b/NEWS
@@ -171,9 +171,6 @@ Security related changes:
   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.
 
@@ -325,6 +322,9 @@ Changes to build and runtime requirements:
 
 Security related changes:
 
+  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-2019-19126: ld.so failed to ignore the LD_PREFER_MAP_32BIT_EXEC
   environment variable during program execution after a security
   transition, allowing local attackers to restrict the possible mapping


                 reply	other threads:[~2020-07-31 11:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200731110000.557A73858D35@sourceware.org \
    --to=fw@sourceware.org \
    --cc=glibc-cvs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).