[MEDIUM] Patch libtpms for CVE-2025-49133

[archana25-ms]

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 libtpms for CVE-2025-49133

• No modification made to the upstream patch.
• Upstream Patch Reference : stefanberger/libtpms@9f9bacc

Change Log

• SPECS/libtpms/CVE-2025-49133.patch
• SPECS/libtpms/libtpms.spec

Does this affect the toolchain?

NO

Links to CVEs

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

Test Methodology

• Patch applies cleanly
  
• Build is successful. -
  libtpms-0.9.6-8.azl3.build.log
• Test is successful. -
  libtpms-0.9.6-8.azl3.test.log

• Pipeline build id: xxxx

[Kanishk-Bansal]

Patch Analysis : the patch applies cleanly

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

[Kanishk-Bansal]

LGTM :)