Skip to content

[HIGH] Patch frr for CVE-2025-61099,CVE-2025-61100,CVE-2025-61101,CVE-2025-61102,CVE-2025-61103,CVE-2025-61104,CVE-2025-61105,CVE-2025-61106 & CVE-2025-61107 #15549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
archana25-ms wants to merge 2 commits into
base: fasttrack/3.0
Choose a base branch
from
Open

[HIGH] Patch frr for CVE-2025-61099,CVE-2025-61100,CVE-2025-61101,CVE-2025-61102,CVE-2025-61103,CVE-2025-61104,CVE-2025-61105,CVE-2025-61106 & CVE-2025-61107 #15549

archana25-ms wants to merge 2 commits into from
+595 −2

Conversation

@archana25-ms
Copy link
Contributor

@archana25-ms archana25-ms commented Jan 21, 2026 •
edited
Loading

…1102,CVE-2025-61103,CVE-2025-61104,CVE-2025-61105,CVE-2025-61106 & CVE-2025-61107

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 frr for CVE-2025-61099,CVE-2025-61100,CVE-2025-61101,CVE-2025-61102,CVE-2025-61103,CVE-2025-61104,CVE-2025-61105,CVE-2025-61106 & CVE-2025-61107

Change Log
Does this affect the toolchain?

NO

Links to CVEs
Test Methodology
  • Pipeline build id: xxxx

@archana25-ms archana25-ms requested a review from a team as a code owner January 21, 2026 11:25
@microsoft-github-policy-service microsoft-github-policy-service bot added Packaging fasttrack/3.0 PRs Destined for Azure Linux 3.0 labels Jan 21, 2026
@Kanishk-Bansal
Copy link
Contributor

Kanishk-Bansal commented Jan 21, 2026

Build

@Kanishk-Bansal
Copy link
Contributor

Kanishk-Bansal commented Jan 21, 2026

/azurepipelines run

@azure-pipelines
Copy link

azure-pipelines bot commented Jan 21, 2026

Azure Pipelines successfully started running 1 pipeline(s).

@archana25-ms
Copy link
Contributor Author

archana25-ms commented Jan 22, 2026

Build

Buddy Build is successful

jslobodzian
jslobodzian requested changes Jan 22, 2026
View reviewed changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jslobodzian jslobodzian jslobodzian requested changes

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

fasttrack/3.0 PRs Destined for Azure Linux 3.0 Packaging security

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@archana25-ms @Kanishk-Bansal @jslobodzian