binutils : Fix CVE-2022-38128
PATCH 1/1 binutils : Fix CVE-2022-38128
From: pgowda <[email protected]>
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=695c6dfe7e85006b98c8b746f3fd5f913c94ebff]
--- .../binutils/binutils-2.38.inc | 3 + .../binutils/0018-CVE-2022-38128-1.patch | 350 ++++++++++++++ .../binutils/0018-CVE-2022-38128-2.patch | 436 ++++++++++++++++++ .../binutils/0018-CVE-2022-38128-3.patch | 95 ++++ 4 files changed, 884 insertions(+) create mode 100644 meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch create mode 100644 meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-2.patch create mode 100644 meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-3.patch
meta/recipes-devtools/binutils/binutils-2.38.inc +3 -0
@@ -39,5 +39,8 @@ SRC_URI = "\ file://0017-CVE-2022-38127-2.patch \ file://0017-CVE-2022-38127-3.patch \ file://0017-CVE-2022-38127-4.patch \ + file://0018-CVE-2022-38128-1.patch \ + file://0018-CVE-2022-38128-2.patch \ + file://0018-CVE-2022-38128-3.patch \ " S = "${WORKDIR}/git"
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patch new file +350 -0
350 lines not on this page · raw message
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-2.patch new file +436 -0
436 lines not on this page · raw message
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-3.patch new file +95 -0
95 lines not on this page · raw message
Signature · 1 line
2.25.1
Hi Pgowda,
Many thanks for your patches!
Quoted 13 lines · Pgowda
From: pgowda <[email protected]>
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=f07c08e115e27cddf5a0030dc6332bbee1bd9c6a]
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=175b91507b83ad42607d2f6dadaf55b7b511bdbe]
Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=695c6dfe7e85006b98c8b746f3fd5f913c94ebff]Signed-off-by pgowda <[email protected]>--- .../binutils/binutils-2.38.inc | 3 + .../binutils/0018-CVE-2022-38128-1.patch | 350 ++++++++++++++ .../binutils/0018-CVE-2022-38128-2.patch | 436 ++++++++++++++++++ .../binutils/0018-CVE-2022-38128-3.patch | 95 ++++ 4 files changed, 884 insertions(+)
Quoted 3 lines
create mode 100644
meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-1.patchcreate mode 100644meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-2.patchcreate mode 100644meta/recipes-devtools/binutils/binutils/0018-CVE-2022-38128-3.patch
Would it be possible to have your "Signed-off-by" and "From" fields with your real name?
That's what is required on https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines ("sorry, no pseudonyms or anonymous contributions").
Another issue is that this stands out in the release notes in the section listing the contributors.
Thanks again
Michael.
Signature · 3 lines
Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com