Skip to content

Patch glibc for CVE-2023-4527, CVE-2023-4806, CVE-2024-33599, CVE-2024-33600, CVE-2024-33601, CVE-2025-0395, CVE-2025-4802 [High] #13864

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

Merged
merged 6 commits into from
Jun 17, 2025

Conversation

Kanishk-Bansal
Copy link
Contributor

@Kanishk-Bansal Kanishk-Bansal commented May 22, 2025

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
Does this affect the toolchain?

YES

Associated issues
Links to CVEs
Test Methodology
Upstream Patch Reference

@Kanishk-Bansal Kanishk-Bansal requested a review from a team May 22, 2025 10:47
@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging specs-extended PR to fix SPECS-EXTENDED fasttrack/3.0 PRs Destined for Azure Linux 3.0 labels May 22, 2025
@Kanishk-Bansal Kanishk-Bansal force-pushed the kanbansal/glibc/CVEs/3.0 branch from e7555e4 to f69f687 Compare May 22, 2025 11:00
…4-33600, CVE-2024-33601, CVE-2025-0395 [High]

Signed-off-by: Kanishk Bansal <kanbansal@microsoft.com>
@Kanishk-Bansal Kanishk-Bansal force-pushed the kanbansal/glibc/CVEs/3.0 branch from f69f687 to a7deb22 Compare May 22, 2025 11:49
@Kanishk-Bansal Kanishk-Bansal marked this pull request as ready for review May 22, 2025 13:00
@Kanishk-Bansal Kanishk-Bansal requested review from a team as code owners May 22, 2025 13:00
Copy link
Contributor

@PawelWMS PawelWMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The patches look good - nice job finding them all and fixing CVE-2023-5156! Leaving a few asks to help with documenting the changes.

@PawelWMS
Copy link
Contributor

Failing ptest are known issues - found no regressions.

@PawelWMS PawelWMS added the CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review label May 22, 2025
Copy link
Contributor

@PawelWMS PawelWMS left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR check fails due to a toolkit bug, not changes in this PR. Running a separate PR check with a slightly modified toolkit to work around that bug has finished fine and reported failing ptests only for known failures. Approving.

@Kanishk-Bansal Kanishk-Bansal changed the title Patch glibc for CVE-2023-4527, CVE-2023-4806, CVE-2024-33599, CVE-2024-33600, CVE-2024-33601, CVE-2025-0395 [High] Patch glibc for CVE-2023-4527, CVE-2023-4806, CVE-2024-33599, CVE-2024-33600, CVE-2024-33601, CVE-2025-0395, CVE-2025-4802 [High] Jun 1, 2025
@Kanishk-Bansal Kanishk-Bansal removed the CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review label Jun 1, 2025
@Kanishk-Bansal Kanishk-Bansal requested a review from PawelWMS June 1, 2025 19:13
@PawelWMS PawelWMS added the CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review label Jun 2, 2025
@jslobodzian jslobodzian merged commit 10c1198 into fasttrack/3.0 Jun 17, 2025
23 of 28 checks passed
@jslobodzian jslobodzian deleted the kanbansal/glibc/CVEs/3.0 branch June 17, 2025 18:56
CBL-Mariner-Bot pushed a commit that referenced this pull request Jun 17, 2025
…024-33600, CVE-2024-33601, CVE-2025-0395, CVE-2025-4802 [High] (#13864)

Signed-off-by: Kanishk Bansal <kanbansal@microsoft.com>
Co-authored-by: Kanishk Bansal <kanbansal@microsoft.com>
Co-authored-by: Pawel Winogrodzki <pawelwi@microsoft.com>
(cherry picked from commit 10c1198)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CVEFixReadyForMaintainerReview When a CVE fix has been reviewed by release manager and is ready for stable maintainer review fasttrack/3.0 PRs Destined for Azure Linux 3.0 Packaging security specs-extended PR to fix SPECS-EXTENDED
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants