From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Christian Stewart <christian@aperture.us>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v1 1/1] package/go: security bump to version go1.22.7
Date: Thu, 19 Sep 2024 21:56:40 +0200 [thread overview]
Message-ID: <87msk3ju2v.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240914110036.13d08b21@windsurf> (Thomas Petazzoni via buildroot's message of "Sat, 14 Sep 2024 11:00:36 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> Hello Christian,
> On Wed, 11 Sep 2024 21:18:58 +0000
> Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
>> Fixes the following CVEs:
>>
>> CVE-2024-34155: go/parser: stack exhaustion in all Parse* functions
>> CVE-2024-34156: encoding/gob: stack exhaustion in Decoder.Decode
>> CVE-2024-34158: go/build/constraint: stack exhaustion in Parse
>>
>> https://go.dev/doc/devel/release#go1.22.7
>>
>> Signed-off-by: Christian Stewart <christian@aperture.us>
>> ---
>> package/go/go-src/go-src.hash | 2 +-
>> package/go/go.mk | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
> I've applied, but your patch was badly line-wrapped. Could you make
> sure to use "git send-email", or adjust your tooling?
Committed to 2024.02.x and 2024.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-09-19 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 21:18 [Buildroot] [PATCH v1 1/1] package/go: security bump to version go1.22.7 Christian Stewart via buildroot
2024-09-14 9:00 ` Thomas Petazzoni via buildroot
2024-09-15 3:07 ` Christian Stewart via buildroot
2024-09-15 7:31 ` Thomas Petazzoni via buildroot
2024-09-15 14:22 ` Christian Stewart via buildroot
2024-09-19 19:56 ` Peter Korsgaard [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=87msk3ju2v.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.