[AutoPR- Security] Patch binutils for CVE-2025-3198 [MEDIUM]

[azurelinux-security]

Auto Patch binutils for CVE-2025-3198.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1121609&view=results

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?

• Auto Patch binutils for CVE-2025-3198 (MEDIUM).

Change Log

• CVE-2025-3198

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-3198

Test Methodology

• Pipeline build id: Buddy Build URL

[AkarshHCL]

Firstly I validated that we are affected to this cve.

As part of validation, I temporarily introduced a deliberate compile error in bucomm.c and ran a test build. The build failed as expected at bucomm.c, which confirms this source file is actively compiled in our build pipeline and that the CVE-affected code path is real for our package.

Also fixed the patch to resolve failing buddy build.