From: Paul Barker <paul@pbarker.dev>
To: Harish.Sadineni@windriver.com, openembedded-core@lists.openembedded.org
Cc: Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH] binutils: Set status for CVE-2025-69646 & CVE-2025-69649
Date: Mon, 06 Apr 2026 09:28:00 +0100 [thread overview]
Message-ID: <aff85443515795d097949cedbf07bd2ed40d7372.camel@pbarker.dev> (raw)
In-Reply-To: <20260406070506.3779367-1-Harish.Sadineni@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1619 bytes --]
On Mon, 2026-04-06 at 00:05 -0700, Sadineni, Harish via
lists.openembedded.org wrote:
> From: Harish Sadineni <Harish.Sadineni@windriver.com>
>
> Set CVE_STATUS for CVE-2025-69646 and CVE-2025-69649, as both CVES are already resolved
> in the latest binutils 2.46 version upgrade.
>
> Signed-off-by: Harish Sadineni <Harish.Sadineni@windriver.com>
> ---
> meta/recipes-devtools/binutils/binutils-2.46.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-devtools/binutils/binutils-2.46.inc b/meta/recipes-devtools/binutils/binutils-2.46.inc
> index ff10050dd9..dc8b6be03e 100644
> --- a/meta/recipes-devtools/binutils/binutils-2.46.inc
> +++ b/meta/recipes-devtools/binutils/binutils-2.46.inc
> @@ -34,3 +34,6 @@ SRC_URI = "\
> file://0013-Define-alignof-using-_Alignof-when-using-C11-or-newe.patch \
> file://0014-Remove-duplicate-pe-dll.o-entry-deom-targ_extra_ofil.patch \
> "
> +
> +CVE_STATUS[CVE-2025-69646] = "fixed-version: Fixed from version 2.46"
Hi Harish,
According to https://nvd.nist.gov/vuln/detail/CVE-2025-69646, the CPE
for CVE-2025-69646 is "cpe:2.3:a:gnu:binutils:2.44:*:*:*:*:*:*:*", so it
should already be seen as fixed in 2.46. Which tool is reporting this as
an unresolved CVE?
> +CVE_STATUS[CVE-2025-69649] = "fixed-version: Fixed from version 2.46"
According to https://nvd.nist.gov/vuln/detail/CVE-2025-69649, the CPE
for this one is "cpe:2.3:a:gnu:binutils:*:*:*:*:*:*:*:*". Please include
some info/links in the commit message to confirm that this was fixed for
v2.46.
Best regards,
--
Paul Barker
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2026-04-06 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 7:05 [PATCH] binutils: Set status for CVE-2025-69646 & CVE-2025-69649 Harish.Sadineni
2026-04-06 8:28 ` Paul Barker [this message]
2026-04-06 9:56 ` [OE-core] " Harish Sadineni
2026-04-08 9:30 ` Paul Barker
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=aff85443515795d097949cedbf07bd2ed40d7372.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=Harish.Sadineni@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--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