From: <Mikko.Rapeli@bmw.de>
To: <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org, bunk@stusta.de
Subject: Re: [PATCH] gcc-9.2: Security fix for CVE-2019-14250
Date: Tue, 3 Sep 2019 05:50:19 +0000 [thread overview]
Message-ID: <20190903055019.GC7889@hiutale> (raw)
In-Reply-To: <438c075e-9284-0eac-5aa0-9599d5c8dffe@gmail.com>
On Mon, Sep 02, 2019 at 02:33:02PM -0700, akuster808 wrote:
>
>
> On 9/2/19 5:40 AM, Adrian Bunk wrote:
> > On Sun, Sep 01, 2019 at 10:07:13AM -0700, akuster808 wrote:
> >>
> >> On 9/1/19 7:05 AM, Adrian Bunk wrote:
> >>> thud and zeus are providing 2 gcc versions each that need fixing.
> >> That is a true statement. What are you expecting?
> > The other versions also being fixed?
> >
> > gcc-8 being fixed in warrior before it gets fixed in master would be
> > the wrong order, and would introduce a security regression in master.
> sent a patch. hope it is what is meant by the above.
>
> >
> > The code should be nearly identical in warrior and master, so fixing
> > this also in gcc-8 in master should be trivial.
> >
> > Fixing gcc-7 in thud would be a bonus.
FWIW, gcc-7-branch of https://github.com/gcc-mirror/gcc.git has this fix already.
-Mikko
commit 740d8b3baeea47cd5407be1752c5159223f77042
Author: rguenth <rguenth@138bc75d-0d04-0410-961f-82ee72b054a4>
AuthorDate: Thu Jul 25 10:50:47 2019 +0000
Commit: rguenth <rguenth@138bc75d-0d04-0410-961f-82ee72b054a4>
CommitDate: Thu Jul 25 10:50:47 2019 +0000
2019-07-25 Richard Biener <rguenther@suse.de>
PR lto/90924
Backport from mainline
2019-07-12 Ren Kimura <rkx1209dev@gmail.com>
* simple-object-elf.c (simple_object_elf_match): Check zero value
shstrndx.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/branches/gcc-7-branch@273795 138bc75d-0d04-0410-961f-82ee72b054a4
diff --git a/libiberty/ChangeLog b/libiberty/ChangeLog
index b785e71..0ecdec0 100644
--- a/libiberty/ChangeLog
+++ b/libiberty/ChangeLog
@@ -1,3 +1,12 @@
+2019-07-25 Richard Biener <rguenther@suse.de>
+
+ PR lto/90924
+ Backport from mainline
+ 2019-07-12 Ren Kimura <rkx1209dev@gmail.com>
+
+ * simple-object-elf.c (simple_object_elf_match): Check zero value
+ shstrndx.
+
2018-12-06 Release Manager
* GCC 7.4.0 released.
prev parent reply other threads:[~2019-09-03 5:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 21:15 [PATCH] gcc-9.2: Security fix for CVE-2019-14250 Armin Kuster
2019-09-01 14:05 ` Adrian Bunk
2019-09-01 17:07 ` akuster808
2019-09-02 12:40 ` Adrian Bunk
2019-09-02 16:10 ` akuster808
2019-09-02 21:33 ` akuster808
2019-09-03 3:41 ` Adrian Bunk
2019-09-03 5:50 ` Mikko.Rapeli [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=20190903055019.GC7889@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=akuster808@gmail.com \
--cc=bunk@stusta.de \
--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