Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Cc: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
Subject: [scarthgap][PATCH v2 0/4] binutils: fix CVE-2025-1147, CVE-2025-8224, CVE-2026-15003, CVE-2026-18220
Date: Wed, 12 Aug 2026 12:54:41 +0200	[thread overview]
Message-ID: <20260812105445.24234-1-jaipaul.cheernam@est.tech> (raw)
In-Reply-To: <20260812072822.22227-1-jaipaul.cheernam@est.tech>

Backport four upstream fixes for binutils 2.42:

- CVE-2025-1147: nm segfault with --ifunc-chars=-- (PR 32556)
- CVE-2025-8224: abort in _bfd_doprnt due to shstrtabsize overflow (PR 32109)
- CVE-2026-15003: buffer overflow in xcoff_link_add_symbols (PR 34053)
- CVE-2026-18220: buffer overflow in elf32_dlx_relocate26

CVE-2025-8224 is adapted for 2.42 (uses _bfd_alloc_and_read instead of
_bfd_mmap_readonly_persistent). All other patches apply cleanly.

Changes v1 -> v2:
- Fixed Upstream-Status placement to be in commit message (before scissors line)

Test results:
  binutils-cross-testsuite 2.42 (x86_64-oe-linux):

  Before:
  binutils: 302 passed, 2 unexpected failures, 1 untested, 7 unsupported
  gas:      1871 passed, 4 unexpected failures, 2 unsupported
  ld:       1728 passed, 5 unexpected failures, 7 expected failures, 1 unresolved, 20 untested, 99 unsupported

  After:
  binutils: 304 passed, 2 unexpected failures, 1 untested, 7 unsupported
  gas:      1871 passed, 4 unexpected failures, 2 unsupported
  ld:       1728 passed, 5 unexpected failures, 7 expected failures, 1 unresolved, 20 untested, 99 unsupported

No regressions. +2 new passes from nm --ifunc-chars=-- tests (CVE-2025-1147).

Jaipaul Cheernam (4):
  binutils: fix CVE-2025-1147
  binutils: fix CVE-2025-8224
  binutils: fix CVE-2026-15003
  binutils: fix CVE-2026-18220

 .../binutils/binutils-2.42.inc                |   4 +
 .../binutils/binutils/CVE-2025-1147.patch     | 110 +++++
 .../binutils/binutils/CVE-2025-8224.patch     |  54 +++
 .../binutils/binutils/CVE-2026-15003.patch    | 400 ++++++++++++++++++
 .../binutils/binutils/CVE-2026-18220.patch    |  65 +++
 5 files changed, 633 insertions(+)
 create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2025-1147.patch
 create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2025-8224.patch
 create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-15003.patch
 create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-18220.patch



  parent reply	other threads:[~2026-08-12 10:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12  7:28 [scarthgap][PATCH 0/4] binutils: fix CVE-2025-1147, CVE-2025-8224, CVE-2026-15003, CVE-2026-18220 Jaipaul Cheernam
2026-08-12  7:28 ` [scarthgap][PATCH 1/4] binutils: fix CVE-2025-1147 Jaipaul Cheernam
2026-08-12  7:48   ` Patchtest results for " patchtest
2026-08-12  7:28 ` [scarthgap][PATCH 2/4] binutils: fix CVE-2025-8224 Jaipaul Cheernam
2026-08-12  7:48   ` Patchtest results for " patchtest
2026-08-12  7:28 ` [scarthgap][PATCH 3/4] binutils: fix CVE-2026-15003 Jaipaul Cheernam
2026-08-12  7:48   ` Patchtest results for " patchtest
2026-08-12  7:28 ` [scarthgap][PATCH 4/4] binutils: fix CVE-2026-18220 Jaipaul Cheernam
2026-08-12  7:48   ` Patchtest results for " patchtest
2026-08-12 10:54 ` Jaipaul Cheernam [this message]
2026-08-12 10:54   ` [scarthgap][PATCH v2 1/4] binutils: fix CVE-2025-1147 Jaipaul Cheernam
2026-08-12 10:54   ` [scarthgap][PATCH v2 2/4] binutils: fix CVE-2025-8224 Jaipaul Cheernam
2026-08-12 10:54   ` [scarthgap][PATCH v2 3/4] binutils: fix CVE-2026-15003 Jaipaul Cheernam
2026-08-12 10:54   ` [scarthgap][PATCH v2 4/4] binutils: fix CVE-2026-18220 Jaipaul Cheernam

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=20260812105445.24234-1-jaipaul.cheernam@est.tech \
    --to=jaipaul.cheernam@est.tech \
    --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