Skip to content

[Low] patch binutils for CVE-2025-1147, CVE-2025-1148, CVE-2025-11839#15458

Open
jykanase wants to merge 2 commits intomicrosoft:3.0-devfrom
jykanase:topic_binutils-3.0
Open

[Low] patch binutils for CVE-2025-1147, CVE-2025-1148, CVE-2025-11839#15458
jykanase wants to merge 2 commits intomicrosoft:3.0-devfrom
jykanase:topic_binutils-3.0

Conversation

@jykanase
Copy link
Contributor

@jykanase jykanase commented Jan 7, 2026

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

patch binutils for CVE-2025-1147, CVE-2025-1148, CVE-2025-11839
Patch Modified: No
CVE-2025-1147 : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=patch;h=7be4186c22f89a87fff048c28910f5d26a0f61ce
CVE-2025-1148 : https://git.launchpad.net/ubuntu/+source/binutils/diff/debian/patches/CVE-2025-1148.patch?id=23551b7f3c0a1881dabbe2051d639bee43261514
CVE-2025-11839 : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=patch;h=12ef7d5b7b02d0023db645d86eb9d0797bc747fe

Change Log
  • binutils.spec
Does this affect the toolchain?

YES

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Local build
Screenshot 2026-01-07 151737 Screenshot 2026-01-07 151838

@jykanase jykanase requested a review from a team as a code owner January 7, 2026 10:06
@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging 3.0-dev PRs Destined for AzureLinux 3.0 labels Jan 7, 2026
@jykanase jykanase force-pushed the topic_binutils-3.0 branch from 1ca0deb to e5c4a10 Compare January 7, 2026 10:08
@Kanishk-Bansal
Copy link
Contributor

Buddy Build

Copy link
Contributor

@Kanishk-Bansal Kanishk-Bansal left a comment

Choose a reason for hiding this comment

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

Patch Analysis (the patch applies cleanly)
Fix for SPECS/binutils/CVE-2025-1148.patch has been taken from Ubuntu as binutils have not released any patch for it yet.

Although the diff shows indentation differences but the developer has applied the patch by patching command and its getting build as well. LGTM

  • Buddy Build 
  • patch applied during the build (check rpm.log)
  • patch include an upstream reference
  • PR has security tag

@Kanishk-Bansal Kanishk-Bansal added the ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review label Jan 9, 2026
@0xba1a
Copy link
Member

0xba1a commented Jan 27, 2026

Patch Analysis (the patch applies cleanly) Fix for SPECS/binutils/CVE-2025-1148.patch has been taken from Ubuntu as binutils have not released any patch for it yet.

Although the diff shows indentation differences but the developer has applied the patch by patching command and its getting build as well. LGTM

  • Buddy Build
  • patch applied during the build (check rpm.log)
  • patch include an upstream reference
  • PR has security tag

@Kanishk-Bansal Thanks for the details. Can you please consider following checks too?

  • Full build as the patch is modifying toolchain packages
  • Individual patch analysis with respect to the vulnerability and security-signoff for backport

@Kanishk-Bansal
Copy link
Contributor

Kanishk-Bansal commented Jan 27, 2026

Patches apply cleanly and no backporting has been done
Full Build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.0-dev PRs Destined for AzureLinux 3.0 Packaging ready-for-stable-review PR has passed initial review and is now ready for a second-level stable maintainer review security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants