From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Yoann Congal" <yoann.congal@smile.fr>, <jeremy.rosen@smile.fr>,
<jackson.james9803@gmail.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [scarthgap][PATCH] glibc: Fix CVEs
Date: Sun, 19 Jul 2026 11:26:02 +0200 [thread overview]
Message-ID: <DK2FUQ2JUE5N.1CFTLSDZJJ0UT@smile.fr> (raw)
In-Reply-To: <DJRMGMKZZY9C.9P908NUEEHAU@smile.fr>
On Mon Jul 6, 2026 at 6:17 PM CEST, Yoann Congal wrote:
> On Mon Jun 8, 2026 at 4:07 PM CEST, J?r?my Rosen via lists.openembedded.org wrote:
>> Hello Jackson
>>
>> from what I see all the CVE are not applied to the upper branches of
>> yocto
>>
>> CVE-2026-5450 is applied to master but not wrynose
>> CVE-2026-5928 is not applied, neither to master nor wrynose.
>>
>> The other three CVE seem to be backported correctly
>>
>> please submit for master/wrynose and the resubmit for scarthgap
>
> Hello Jackson,
>
> Gentle ping for this patch needing patches for more recent branches.
> Also:
> * Please put the CVE id in the patch titles "Fix CVEs" is a bit too
> vague.
> * glibc CVEs are usualy handled via upgrades along the stable branch
> instead of backporting individual patches.
> * Nitpick: the CVE patches are usualy simply named "CVE-XXX-YYYY.patch"
I will now drop this patch in favor of the glibc upgrade patch received
in the meantime.
Thanks!
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-07-19 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 4:28 [scarthgap][PATCH] glibc: Fix CVEs Jackson James
2026-06-08 14:07 ` [OE-core] " Jérémy Rosen
2026-07-06 16:17 ` Yoann Congal
2026-07-19 9:26 ` 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=DK2FUQ2JUE5N.1CFTLSDZJJ0UT@smile.fr \
--to=yoann.congal@smile.fr \
--cc=jackson.james9803@gmail.com \
--cc=jeremy.rosen@smile.fr \
--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