[Medium] Patch rust for CVE-2026-25541, CVE-2026-25727, CVE-2025-58160, CVE-2026-27171

[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

Patch rust for CVE-2025-58160, CVE-2026-25541, CVE-2026-25727

• CVE-2025-58160 [Low]:
  patch modified: No
• CVE-2026-25541 [Medium]:
  patch modified: Yes
  Backported manually to support upstream logic in bytes_mut.rs and added testcases for backported code in file test_bytes.rs from upstream.
  Astrolabe reference: tokio-rs/bytes@d0293b0
• CVE-2026-25727 [Medium]:
  patch modified: No
• CVE-2026-27171 [Low]:
  patch modified: No

Change Log

• new file: SPECS/rust/CVE-2025-58160.patch
• new file: SPECS/rust/CVE-2026-25541.patch
• new file: SPECS/rust/CVE-2026-25727.patch
• new file: SPECS/rust/CVE-2026-27171.patch
• modified: SPECS/rust/rust.spec

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2025-58160
• https://nvd.nist.gov/vuln/detail/CVE-2026-25541
• https://nvd.nist.gov/vuln/detail/CVE-2026-25727
• https://nvd.nist.gov/vuln/detail/CVE-2026-27171

Test Methodology

• Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1051441&view=results

[KavyaSree2610]

Patch Analysis (the patch applies cleanly)

• Buddy Build successful
• Patch applied during the build (check rpm.log)

• Patches include an upstream reference
• PR has security tag

[kgodara912]

Could you please recheck one patch? Other two patches look fine and matches with upstream reference.

[kgodara912]

This patch has poor indentation and multiple things which are not present in upstream patch for both the references. Could you please check once the other backports of this CVE and see if we could improve this backported patch. We can keep test cases if they are working as expected.

[BinduSri-6522866]

Fixed and updated.

[kgodara912]

Buddy build after recent corrections.

[BinduSri-6522866]

Buddy build passed.

[kgodara912]

Patches are almost identical to upstream changes except one which is backported, though checksum file changes make them look too big. Buddy build is successful and above comment shows that they are applied too. LGTM.