Skip to contentSkip to conversation

gcc-8.3: Security fix for CVE-2019-14250

PATCH In review Armin Kuster 2 participants 2 messages Aug 31, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 gcc-8.3: Security fix for CVE-2019-14250

From: Armin Kuster <[email protected]>

Affects < 9.2

---
 meta/recipes-devtools/gcc/gcc-8.3.inc              |  1 +
 .../gcc/gcc-8.3/CVE-2019-14250.patch               | 44 ++++++++++++++++++++++
 2 files changed, 45 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc-8.3/CVE-2019-14250.patch
meta/recipes-devtools/gcc/gcc-8.3.inc +1 -0
index dce85a2..80f716a 100644
@@ -74,6 +74,7 @@ SRC_URI = "\
            file://0041-Add-a-recursion-limit-to-libiberty-s-demangling-code.patch \
            file://0042-PR-debug-86964.patch \
            file://0043-PR85434-Prevent-spilling-of-stack-protector-guard-s-.patch \
+           file://CVE-2019-14250.patch \
 "
 SRC_URI[md5sum] = "65b210b4bfe7e060051f799e0f994896"
 SRC_URI[sha256sum] = "64baadfe6cc0f4947a84cb12d7f0dfaf45bb58b7e92461639596c21e02d97d2c"
meta/recipes-devtools/gcc/gcc-8.3/CVE-2019-14250.patch new file +44 -0

44 lines not on this page · raw message

Signature · 1 line
2.7.4
#1 lore raw

✗ patchtest: failure for gcc-8.3: Security fix for CVE-2019-14250

== Series Details ==

Series: gcc-8.3: Security fix for CVE-2019-14250
Revision: 1
URL : https://patchwork.openembedded.org/series/19612/
State : failure

== Summary ==

Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures:

* Issue Series does not apply on top of target branch [test_series_merge_on_head]
Suggested fix Rebase your series on top of targeted branch
Targeted branch warrior (currently at 952bfcc3f4)

If you believe any of these test results are incorrect, please reply to the mailing list ([email protected]) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...).

---

Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe