[Low] patch elfutils for CVE-2025-1352

[durgajagadeesh]

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 elfutils for CVE-2025-1352

Change Log

• CVE-2025-1352

Does this affect the toolchain?

NO

Associated issues

• #xxxx

Links to CVEs

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

Test Methodology

• Verified patches are applied

[mfrw]

test build failure link

[mfrw]

Retriggered: link

[kgodara912]

Patch matches with upstream reference. Buddy build succeeded. @durgajagadeesh, You are claiming that you have built toolchain, did you actually build it?
The toolchain has been rebuilt successfully (or no changes were made to it)

Retriggered: link

@mfrw, This trigger is buddy build local where sources are downloaded from upstream instead of blob-store.

[0xba1a]

Patch matches with upstream reference. Buddy build succeeded. @durgajagadeesh, You are claiming that you have built toolchain, did you actually build it? The toolchain has been rebuilt successfully (or no changes were made to it)

Retriggered: link

@mfrw, This trigger is buddy build local where sources are downloaded from upstream instead of blob-store.

Waiting for full build as the toolchain package change.
Expecting @kgodara912 to verify that.

[kgodara912]

Triggered toolchain build with the PR. Will update with results --> Toolchain is building fine with this change.

[kgodara912]

Build build is succeeded and toolchain is building fine. LGTM.

[0xba1a]

Discussed with @kgodara912 offline. Triggering a full-build based on that discussion.

[kgodara912]

Full build

[kgodara912]

Full build is also successfull except one [ARM64-2-OneBranch]-Dev-BuildRpms → for which package build is successful, but at the end

Configuring Azure CLI to install extensions and use mariner org
ERROR: Request to https://github.com/Azure/azure-devops-cli-extension/releases/download/20240514.1/azure_devops-1.0.1-py2.py3-none-any.whl failed with 500

which seems unrelated to this PR. LGTM.