Skip to content

Conversation

@BinduSri-6522866
Copy link
Contributor

@BinduSri-6522866 BinduSri-6522866 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

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
Test Methodology
image
  • Installation Check:
image
  • Uninstallation Check:
image

@BinduSri-6522866 BinduSri-6522866 marked this pull request as ready for review January 7, 2026 15:48
@BinduSri-6522866 BinduSri-6522866 requested a review from a team as a code owner January 7, 2026 15:48
@Kanishk-Bansal
Copy link
Contributor

Buddy Build

@BinduSri-6522866
Copy link
Contributor Author

Buddy build failed for arm64. Because rpm-ostree is ExclusiveArch: x86_64.
And test failure existed previously.

Copy link
Contributor

@bhagyapathak bhagyapathak 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 (Minor Changes) The absence of CHANGELOG.md and Cargo.toml changes in patch file is acceptable because these are upstream metadata files not critical for the security fix

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

@bhagyapathak bhagyapathak 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

main PR Destined for main 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