From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Yoann Congal" <yoann.congal@smile.fr>, <hprajapati@mvista.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [scarthgap][PATCH] gnutls: fix for CVE-2026-42011
Date: Thu, 23 Jul 2026 12:01:52 +0200 [thread overview]
Message-ID: <DK5V4C4OR0LU.3TX4H3M608KI4@smile.fr> (raw)
In-Reply-To: <DK389JR4BTT8.24WAJUMLMD609@smile.fr>
On Mon Jul 20, 2026 at 9:41 AM CEST, Yoann Congal wrote:
> On Sun Jul 19, 2026 at 5:10 PM CEST, Yoann Congal wrote:
>> On Mon Jun 29, 2026 at 12:27 AM CEST, Yoann Congal wrote:
>>> On Thu Jun 25, 2026 at 2:55 PM CEST, Hitendra Prajapati via lists.openembedded.org wrote:
>>>> Pick patch from [1] & [2] also mentioned at Debian report in [3]
>>>>
>>>> [1] https://gitlab.com/gnutls/gnutls/-/commit/1dead2faec6320aaba321eb56f20d442df192b83
>>>> [2] https://gitlab.com/gnutls/gnutls/-/commit/24713b8c63137ce0665b495d22ccce4f5ce05c84
>>>> [3] https://security-tracker.debian.org/tracker/CVE-2026-42011
>>>> [4] https://gitlab.com/gnutls/gnutls/-/work_items/1824
>>>>
>>>> Signed-off-by: Hitendra Prajapati <hprajapati@mvista.com>
>>>> ---
>>>
>>> As far as I know, this fix is also needed on wrynose:
>>> CVE-2026-42011 is fixed in 3.8.13 per Debian Security Tracker but wrynose has 3.8.12.
>>>
>>> Can you send a fix for wrynose so I can take this one for scarthgap?
>>>
>>> Thanks!
>>
>
> Hello,
>
>> Here the current state of this series: Hold pending an equivalent merge on wrynose.
>> v1 series received here:
>> [OE-core] [wrynose] [PATCH 1/6] curl: ignore CVE-2026-4873
>> https://lore.kernel.org/all/20260629131453.1077612-1-adongare@cisco.com/
>> but had reviews and no v2.
> Self-replying: ^ this is wrong. this gnutls scarthgap patch does not
> depend on a wrynose curl patch but on this one (received in the
> meantime):
> https://lore.kernel.org/all/20260720065644.24395-1-hprajapati@mvista.com/
As a status update: this scarthgap series is blocked on a v2 sent for
the wrynose series.
My plan is to drop this series in a few week if the above situation does
not change.
Regards,
--
Yoann Congal
Smile ECS
prev parent reply other threads:[~2026-07-23 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 12:55 [scarthgap][PATCH] gnutls: fix for CVE-2026-42011 Hitendra Prajapati
2026-06-28 22:27 ` [OE-core] " Yoann Congal
2026-07-19 15:02 ` Yoann Congal
2026-07-20 7:07 ` Hitendra Prajapati
2026-07-19 15:10 ` Yoann Congal
2026-07-20 7:41 ` Yoann Congal
2026-07-23 10:01 ` 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=DK5V4C4OR0LU.3TX4H3M608KI4@smile.fr \
--to=yoann.congal@smile.fr \
--cc=hprajapati@mvista.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