Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <sudumbha@cisco.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][PATCH 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442
Date: Fri, 08 May 2026 00:03:37 +0200	[thread overview]
Message-ID: <DICS8ZZ99Q7C.25QI9TUSM1VCB@smile.fr> (raw)
In-Reply-To: <20260502142354.3840615-1-sudumbha@cisco.com>

On Sat May 2, 2026 at 4:23 PM CEST, Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco) via lists.openembedded.org wrote:
> From: Sudhir Dumbhare <sudumbha@cisco.com>
>
> This patch applies the upstream fix [1], which addresses two out-of-bounds
> read issues in bfd/xcofflink.c within xcoff_link_add_symbols(). The changes
> shown in [2] are referenced by [3] and [4].
>
> [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=c2bf7de1eb77a91d7a3c86d56408bf57de540faf
> [2] https://sourceware.org/git/?p=binutils-gdb.git;a=blobdiff;f=bfd/xcofflink.c;h=1781182fa6a3f92e5e91996f8b0dcf3ab192679b;hp=fde21c9f9583baff05e72e390e6bb896d02f9d43;hb=c2bf7de1eb77a91d7a3c86d56408bf57de540faf;hpb=d7f532cb3a46527
> [3] https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-3441
> [4] https://bugzilla.suse.com/show_bug.cgi?id=CVE-2026-3442
>
> Reference:
> https://nvd.nist.gov/vuln/detail/CVE-2026-3441
> https://nvd.nist.gov/vuln/detail/CVE-2026-3442
> https://www.suse.com/security/cve/CVE-2026-3441.html
> https://www.suse.com/security/cve/CVE-2026-3442.html
>
> Signed-off-by: Sudhir Dumbhare <sudumbha@cisco.com>
> ---
>  .../binutils/binutils-2.42.inc                |  1 +
>  .../CVE-2026-3441_CVE-2026-3442.patch         | 50 +++++++++++++++++++
>  2 files changed, 51 insertions(+)
>  create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-3441_CVE-2026-3442.patch
>
> diff --git a/meta/recipes-devtools/binutils/binutils-2.42.inc b/meta/recipes-devtools/binutils/binutils-2.42.inc
> index 839d31242e..5d91a41648 100644
> --- a/meta/recipes-devtools/binutils/binutils-2.42.inc
> +++ b/meta/recipes-devtools/binutils/binutils-2.42.inc
> @@ -69,5 +69,6 @@ SRC_URI = "\
>       file://0028-CVE-2025-11494.patch \
>       file://0029-CVE-2025-11839.patch \
>       file://0030-CVE-2025-11840.patch \
> +     file://CVE-2026-3441_CVE-2026-3442.patch \
>  "
>  S  = "${WORKDIR}/git"
> diff --git a/meta/recipes-devtools/binutils/binutils/CVE-2026-3441_CVE-2026-3442.patch b/meta/recipes-devtools/binutils/binutils/CVE-2026-3441_CVE-2026-3442.patch
> new file mode 100644
> index 0000000000..28cface2c9
> --- /dev/null
> +++ b/meta/recipes-devtools/binutils/binutils/CVE-2026-3441_CVE-2026-3442.patch
> @@ -0,0 +1,50 @@
> +From 88a051b765a7684b24250907c2dad9fa8cd4124a Mon Sep 17 00:00:00 2001
> +From: Alan Modra <amodra@gmail.com>
> +Date: Sat, 28 Feb 2026 13:16:40 +1030
> +Subject: [PATCH] xcofflink buffer overflows
> +
> +This fixes two fuzzed object file out-of-bounds accesses.
> +
> +	* xcofflink.c (xcoff_link_add_symbols): Properly bounds check
> +	XTY_LD x_scnlen index.  Sanity check r_symndx before using it
> +	to index sym hashes.
> +
> +CVE: CVE-2026-3441 CVE-2026-3442
> +Upstream-Status: Backport [https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=c2bf7de1eb77a91d7a3c86d56408bf57de540faf]
> +
> +(cherry picked from commit c2bf7de1eb77a91d7a3c86d56408bf57de540faf)
> +Signed-off-by: Sudhir Dumbhare <sudumbha@cisco.com>
> +---
> + bfd/xcofflink.c | 10 ++++------
> + 1 file changed, 4 insertions(+), 6 deletions(-)
> +

Hello,

This patch has a weird format:

> +diff --git a/bfd/xcofflink.c b/bfd/xcofflink.c
> +index e0165d202a9..88c49755c64 100644
> +--- a/bfd/xcofflink.c
> ++++ b/bfd/xcofflink.c
> +@@ -1873,12 +1873,9 @@ xcoff_link_add_symbols (bfd *abfd, struct bfd_link_info *info)
> +	     follow its appropriate XTY_SD symbol.  The .set pseudo op can
   ^ here a context line starts with a TAB instead of the usual space.
     Can you check please?

> +	     cause the XTY_LD to not follow the XTY_SD symbol. */
> +	  {
> +-	    bool bad;
> +-
> +-	    bad = false;
> +-	    if (aux.x_csect.x_scnlen.u64
> +-		>= (size_t) (esym - (bfd_byte *) obj_coff_external_syms (abfd)))
> +-	      bad = true;
> ++	    bool bad = (aux.x_csect.x_scnlen.u64
> ++			>= ((esym - (bfd_byte *) obj_coff_external_syms (abfd))
> ++			    / symesz));
> +	    if (! bad)
> +	      {
> +		section = xcoff_data (abfd)->csects[aux.x_csect.x_scnlen.u64];
> +@@ -2244,6 +2241,7 @@ xcoff_link_add_symbols (bfd *abfd, struct bfd_link_info *info)
> +		 functions imported from dynamic objects.  */
> +	      if (info->output_bfd->xvec == abfd->xvec
> +		  && *rel_csect != bfd_und_section_ptr
> ++		  && (unsigned long) rel->r_symndx < obj_raw_syment_count (abfd)
> +		  && obj_xcoff_sym_hashes (abfd)[rel->r_symndx] != NULL)
> +		{
> +		  struct xcoff_link_hash_entry *h;
> +--
     ^ Also, this line usually has a ending space. Maybe some tool
       decided to rewrite spaces, unaware of the patch expected format?

Thanks!

> +2.44.4


-- 
Yoann Congal
Smile ECS



  parent reply	other threads:[~2026-05-07 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-02 14:23 [OE-core][scarthgap][PATCH 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-05-02 14:23 ` [OE-core][scarthgap][PATCH 2/2] binutils: fix CVE-2026-4647 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-05-07 22:03 ` Yoann Congal [this message]
2026-05-13 17:27   ` [OE-core][scarthgap][PATCH v2 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-05-13 17:27     ` [OE-core][scarthgap][PATCH v2 2/2] binutils: fix CVE-2026-4647 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-03 21:09       ` Yoann Congal
2026-07-06 10:43         ` Yoann Congal
2026-06-03 21:02     ` [OE-core][scarthgap][PATCH v2 1/2] binutils: fix CVE-2026-3441 and CVE-2026-3442 Yoann Congal
2026-05-13 17:39   ` [scarthgap][PATCH " Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)

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=DICS8ZZ99Q7C.25QI9TUSM1VCB@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sudumbha@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox