Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <Harish.Sadineni@windriver.com>, <paul@pbarker.dev>,
	<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: Mon, 20 Jul 2026 08:23:01 +0200	[thread overview]
Message-ID: <DK36L51LLLOK.39Q32176DFBIF@smile.fr> (raw)
In-Reply-To: <ed5831c1-386c-4463-8ff2-74a660fef088@windriver.com>

On Mon Jul 20, 2026 at 8:03 AM CEST, Harish via lists.openembedded.org Sadineni wrote:
> On 19-07-2026 02:36 pm, Yoann Congal wrote:
>
>> CAUTION: This email comes from a non Wind River email account!
>> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>>
>> 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
> Hi Paul, Yoann,
>
> Here's more concrete evidence of the duplication:
>
> Bugzilla bug 33641 (assigned CVE-2025-69648) has been resolved as a 
> duplicate of bug 33638 (assigned CVE-2025-69646):
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=33641
>
> Do you want me to send a v2 with this info added to the commit message, 
> or is this sufficient as-is?

Hello,

A v2 with the added info please :)

Thanks!

>
> Thanks,
> Harish
>>
>> Regards,
>> --
>> Yoann Congal
>> Smile ECS
>>


-- 
Yoann Congal
Smile ECS



      reply	other threads:[~2026-07-20  6:23 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   ` [OE-core] " Yoann Congal
2026-07-20  6:03     ` Harish Sadineni
2026-07-20  6:23       ` Yoann Congal [this message]

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=DK36L51LLLOK.39Q32176DFBIF@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