All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yash Shinde <yashinde145@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: rwmacleod@gmail.com, umesh.kalappa0@gmail.com,
	pgowda.cve@gmail.com, sundeep.kokkonda@gmail.com,
	shivams@gmail.com, Yash Shinde <yashinde145@gmail.com>
Subject: [kirkstone] [PATCH] Binutils : Fix CVE-2022-4285
Date: Tue, 20 Dec 2022 17:48:24 +0530	[thread overview]
Message-ID: <20221220121824.3299590-1-yashinde145@gmail.com> (raw)

Upstream-Status: Backport [https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5c831a3c7f3ca98d6aba1200353311e1a1f84c70]

Signed-off-by: Yash Shinde <yashinde145@gmail.com>
---
 .../binutils/binutils/0019-CVE-2022-4285.patch                 | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-devtools/binutils/binutils/0019-CVE-2022-4285.patch b/meta/recipes-devtools/binutils/binutils/0019-CVE-2022-4285.patch
index 4f8ffce1de..0ad93081f9 100644
--- a/meta/recipes-devtools/binutils/binutils/0019-CVE-2022-4285.patch
+++ b/meta/recipes-devtools/binutils/binutils/0019-CVE-2022-4285.patch
@@ -9,7 +9,10 @@ Subject: [PATCH] Fix an illegal memory access when parsing an ELF file
 	of the section header is zero.
 
 Upstream-Status: Backport
+CVE: CVE-2022-4285
+
 [https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5c831a3c7f3ca98d6aba1200353311e1a1f84c70]
+
 ---
  bfd/ChangeLog | 6 ++++++
  bfd/elf.c     | 4 +++-
-- 
2.25.1



             reply	other threads:[~2022-12-20 12:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20 12:18 Yash Shinde [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-20 13:12 [kirkstone] [PATCH] binutils : Fix CVE-2022-4285 Yash Shinde
2022-12-21 18:11 Yash Shinde
2022-12-22 14:36 [OE-core] " Steve Sakoman
2022-12-27 16:54 ` Yash Shinde

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=20221220121824.3299590-1-yashinde145@gmail.com \
    --to=yashinde145@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pgowda.cve@gmail.com \
    --cc=rwmacleod@gmail.com \
    --cc=shivams@gmail.com \
    --cc=sundeep.kokkonda@gmail.com \
    --cc=umesh.kalappa0@gmail.com \
    /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.