From: "Cedric Veilleux" <veilleux.cedric@gmail.com>
To: "Yoann Congal" <yoann.congal@smile.fr>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] go regression in scarthgap related to CVE-2025-61726 patch
Date: Wed, 11 Mar 2026 13:36:21 -0700 [thread overview]
Message-ID: <375609.1773261381723955240@lists.yoctoproject.org> (raw)
In-Reply-To: <DH070BEBCNFR.351WN55RVTJLH@smile.fr>
On Wed, Mar 11, 2026 at 03:16 PM, Yoann Congal wrote:
>
> Is this problem related to this patch under review?
> go: Fix CVE-2025-61726.patch variable ordering
> https://git.openembedded.org/openembedded-core-contrib/commit/?h=stable/scarthgap-nut&id=9605a264c87b5c7ce26eeec902448b0892f8af1a
>
> Could you try to see if that fixes your problem and report back?
>
Confirmed. The above patch fixes the issue, my podman binary is working again.
Thank you!
Cedric
prev parent reply other threads:[~2026-03-11 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 18:18 go regression in scarthgap related to CVE-2025-61726 patch Cedric Veilleux
2026-03-11 19:16 ` [yocto] " Yoann Congal
2026-03-11 20:36 ` Cedric Veilleux [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=375609.1773261381723955240@lists.yoctoproject.org \
--to=veilleux.cedric@gmail.com \
--cc=yoann.congal@smile.fr \
--cc=yocto@lists.yoctoproject.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