From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] binutils CVE fixes for CVE-2026-91781, CVE-2026-91782 and CVE-2026-90828
Date: Wed, 18 Nov 2026 16:20:08 +0100 [thread overview]
Message-ID: <20261118152011.24213-1-jaipaul.cheernam@est.tech> (raw)
- Same patches will be backported to blacksail onces its merged to master
Jaipaul Cheernam (3):
binutils: Patch CVE-2026-91781
binutils: Patch for CVE-2026-90828
binutils: Patch for CVE-2026-91782
.../binutils/binutils-2.47.inc | 7 +
.../binutils/binutils/CVE-2026-90828.patch | 29 ++
.../binutils/binutils/CVE-2026-91781.patch | 36 ++
.../binutils/binutils/CVE-2026-91782-1.patch | 80 ++++
.../binutils/binutils/CVE-2026-91782-2.patch | 424 ++++++++++++++++++
.../binutils/binutils/CVE-2026-91782-3.patch | 130 ++++++
.../binutils/binutils/CVE-2026-91782-4.patch | 50 +++
.../binutils/binutils/CVE-2026-91782-5.patch | 65 +++
8 files changed, 821 insertions(+)
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-90828.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-91781.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-91782-1.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-91782-2.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-91782-3.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-91782-4.patch
create mode 100644 meta/recipes-devtools/binutils/binutils/CVE-2026-91782-5.patch
next reply other threads:[~2026-11-18 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 15:20 Jaipaul Cheernam [this message]
2026-11-18 15:20 ` [PATCH 1/3] binutils: Patch CVE-2026-91781 Jaipaul Cheernam
2026-11-18 15:20 ` [PATCH 2/3] binutils: Patch for CVE-2026-90828 Jaipaul Cheernam
2026-11-18 15:20 ` [PATCH 3/3] binutils: Patch for CVE-2026-91782 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=20261118152011.24213-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