-
Notifications
You must be signed in to change notification settings - Fork 589
[HIGH] Patch golang 1.22.7 for CVE-2025-4674 #14427
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: fasttrack/2.0
Are you sure you want to change the base?
[HIGH] Patch golang 1.22.7 for CVE-2025-4674 #14427
Conversation
of the existing PolicyIdentifiers field, by using the | ||
[`x509usepolicies` setting.](/pkg/crypto/x509/#CreateCertificate). | ||
|
||
+Go 1.22.7 disabled build information stamping when multiple VCS are detected due |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Although this is not an issue here as it is just text - We would probably not want to change this.
From what I recall Go 1.23.11 disabled build information stamping, and not 1.22 :)
Date: Mon, 9 Jun 2025 11:23:46 -0700 | ||
Subject: [PATCH] [release-branch.go1.23] cmd/go: disable support for multiple | ||
vcs in one module | ||
Upstream Patch Reference: https://github.com/golang/go/commit/e9d2c032b14c17083be0f8f0c822565199d2994f |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Patch Applies Cleanly
Slight back port for this patch was needed
Patch looks good to me apart from a slight change which is text only.
Signed-Off By: Muhammad Falak
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Triggered Test Build
|
Updated |
From the Buddy-build, build is successful for both amd64 & arm64, also tests have run successfully. |
Merge Checklist
All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)
*-static
subpackages, etc.) have had theirRelease
tag incremented../cgmanifest.json
,./toolkit/scripts/toolchain/cgmanifest.json
,.github/workflows/cgmanifest.json
)./LICENSES-AND-NOTICES/SPECS/data/licenses.json
,./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md
,./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON
)*.signatures.json
filessudo make go-tidy-all
andsudo make go-test-coverage
passSummary
What does the PR accomplish, why was it needed?
Patch golang 1.22.7 for CVE-2025-4674
Change Log
Does this affect the toolchain?
NO
Links to CVEs
Test Methodology
golang-1.22.7-5.cm2.src.rpm.log