From: "Yoann Congal" <yoann.congal@smile.fr>
To: <paul@pbarker.dev>, <Harish.Sadineni@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: <Sundeep.Kokkonda@windriver.com>
Subject: Re: [OE-core] [scarthgap][PATCH] binutils: Add CVE-2025-69646 to "CVE:" tag
Date: Sun, 19 Jul 2026 11:06:28 +0200 [thread overview]
Message-ID: <DK2FFQBSC7HA.15XI81YMBOZY@smile.fr> (raw)
In-Reply-To: <d9b4dfb530a0898fd230ad6da09ee7bf90dd063a.camel@pbarker.dev>
On Tue Jul 14, 2026 at 2:53 PM CEST, Paul Barker via lists.openembedded.org wrote:
> On Mon, 2026-07-06 at 02:06 -0700, Harish.Sadineni@windriver.com wrote:
>> From: Harish Sadineni <Harish.Sadineni@windriver.com>
>>
>> CVE-2025-69648 was marked as a duplicate of CVE-2025-69646. The
>> existing patch already fixes the issue associated with both CVEs.
>
> Hi Harish,
>
> Where was this marked as a duplicate? We need a link to some evidence of
> this, or at least a more thorough explanation.
Hello,
FYI, when reviewing this I took the fact that both NVD entries[0][1] point to the
same patch[2] as proof of duplication (albeit weak).
[0]: https://nvd.nist.gov/vuln/detail/CVE-2025-69648
[1]: https://nvd.nist.gov/vuln/detail/CVE-2025-69646
[2]: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=598704a00cbac5e85c2bedd363357b5bf6fcee33
Regards,
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-07-19 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 9:06 [scarthgap][PATCH] binutils: Add CVE-2025-69646 to "CVE:" tag Harish.Sadineni
2026-07-14 12:53 ` Paul Barker
2026-07-19 9:06 ` Yoann Congal [this message]
2026-07-20 6:03 ` [OE-core] " Harish Sadineni
2026-07-20 6:23 ` Yoann Congal
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=DK2FFQBSC7HA.15XI81YMBOZY@smile.fr \
--to=yoann.congal@smile.fr \
--cc=Harish.Sadineni@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@pbarker.dev \
/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