[Low] Patch rpm-ostree for CVE-2025-58160

[BinduSri-6522866]

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?
Patch rpm-ostree for CVE-2025-58160
patch modified: Yes

• Did not applied patch for tracing-subscriber/CHANGELOG.md and tracing-subscriber/Cargo.toml files, as those changes are not part of CVE fix.
• Astrolabe Patch Reference: tokio-rs/tracing@4c52ca5

Change Log

• new file: ../SPECS/rpm-ostree/CVE-2025-58160.patch
• modified: ../SPECS/rpm-ostree/rpm-ostree.spec

Does this affect the toolchain?

NO

Links to CVEs

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

Test Methodology

• Local Build:
  rpm-ostree-2024.4-6.azl3.src.rpm.log
  rpm-ostree-2024.4-6.azl3.src.rpm.test.log
• Patch applies cleanly:

• Installation Check:

• Uninstallation Check:

[Kanishk-Bansal]

Buddy Build

[BinduSri-6522866]

Buddy build failed for arm64. Because rpm-ostree is ExclusiveArch: x86_64

[bhagyapathak]

Patch Analysis (Minor Changes)

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

[kgodara912]

Please check why it was reverted, https://github.com/ricky26/tracing/commit/2e1c50bb8fd40c32da5004894d893251473f47f9

[kgodara912]

Please check why it was reverted, https://github.com/ricky26/tracing/commit/2e1c50bb8fd40c32da5004894d893251473f47f9

[BinduSri-6522866]

The upstream change from PR tokio-rs/tracing#3368 (see commit tokio-rs/tracing@4c52ca5) was reverted in tokio-rs/tracing because it introduced behavioral and compatibility regressions tokio-rs/tracing#3369.
This commit ricky26/tracing@2e1c50b corrects that change by reverting PR #3368.