Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: "Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at
	Cisco)" <hthakar@cisco.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "xe-linux-external (Internal Group)"
	<xe-linux-external@cisco.com>,
	 Yoann Congal <yoann.congal@smile.fr>
Subject: Re: [OE-core][scarthgap][PATCH 1/2] go: Fix CVE-2026-33814
Date: Mon, 19 Oct 2026 12:09:38 +0100	[thread overview]
Message-ID: <92b3723f22c7eaef6c21cedbde230c4eb3f3ee38.camel@pbarker.dev> (raw)
In-Reply-To: <PH7PR11MB85988110C1425A7BD276918FAD982@PH7PR11MB8598.namprd11.prod.outlook.com>

On Mon, 2026-10-19 at 09:52 +0000, Hetvi Thakar -X (hthakar - E
INFOCHIPS PRIVATE LIMITED at Cisco) wrote:
> Hi Paul, Yoann,
> 
> Thanks for the review.
> 
> The go.mod, go.sum, and vendor/modules.txt changes are not required for this Go 1.22 backport, as the upstream Go 1.25 commit updates the entire x/net dependency to revision a9171bc8 [1].
> 
> For Go 1.22, the required security fix is applied directly to src/net/http/h2_bundle.go [2]. The fix addresses the infinite CONTINUATION frame loop described in the CVE.
> 
> Updating only the dependency metadata without updating the complete vendored x/net source would be inconsistent. Since this is a focused security backport, the dependency update is not needed.
> 
> The additional validation-related change in the upstream commit is not applicable to Go 1.22, as the corresponding code is not present in this version [2].
> 
> References:
> [1] https://go.googlesource.com/net/+/a9171bc8c6f19c50efad8880f96e361359ed5307%5E%21/
> [2] https://github.com/golang/go/blob/go1.22.12/src/net/http/h2_bundle.go

Hi Hetvi,

If you've checked this and you're confident that the go.mod/go.sum
changes are not needed then this patch can go ahead.

Best regards,

-- 
Paul Barker



      reply	other threads:[~2026-10-19 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  6:14 [OE-core][scarthgap][PATCH 1/2] go: Fix CVE-2026-33814 Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-08-31  6:14 ` [OE-core][scarthgap][PATCH 2/2] go: Fix CVE-2026-39823 Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-09-17 13:58 ` [OE-core][scarthgap][PATCH 1/2] go: Fix CVE-2026-33814 Paul Barker
2026-10-19  9:52   ` Hetvi Thakar -X (hthakar - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-10-19 11:09     ` Paul Barker [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=92b3723f22c7eaef6c21cedbde230c4eb3f3ee38.camel@pbarker.dev \
    --to=paul@pbarker.dev \
    --cc=hthakar@cisco.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=xe-linux-external@cisco.com \
    --cc=yoann.congal@smile.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox