[AutoPR- Security] Patch libvirt for CVE-2026-63623, CVE-2026-63622, CVE-2026-61477 [HIGH]

[Azure Linux Security Servicing Account (azurelinux-security)]

Auto Patch libvirt for CVE-2026-63623, CVE-2026-63622, CVE-2026-61477.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1181882&view=results

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?

• Auto Patch libvirt for CVE-2026-63623 (MEDIUM), CVE-2026-63622 (HIGH), CVE-2026-61477 (LOW).

Change Log

• CVE-2026-63623
• CVE-2026-63622
• CVE-2026-61477

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-63623
• https://nvd.nist.gov/vuln/detail/CVE-2026-63622
• https://nvd.nist.gov/vuln/detail/CVE-2026-61477

Test Methodology

• Pipeline build id: Buddy Build URL

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[durgajagadeesh]

CVE-2026-63623[Medium]

1. The AI patch includes an upstream patch reference.
2. The AI patch matches the upstream patch.
3. backport: No.

CVE-2026-63622[High]

1. The AI patch includes an upstream patch reference.
2. The AI patch matches the upstream patch.
3. backport: No.

CVE-2026-61477[Low]:

1. The AI patch includes an upstream patch reference.
2. The patch has been backported manually.
3. The AI patch added one if condition from extra commit changes in conf.c, which was not present in astrolabe. I removed that if condition.
4. One of the commits includes test file changes, but our source code does not have those test files. So the AI patch skipped those file changes.
5. The patch now matches the upstream patch.
6. Buddy build: passes and patch applied cleanly.

[Kanishk Bansal (Kanishk-Bansal)]

/azurepipelines run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

[Aditya Singh (v-aaditya)]

Peer-review analysis -

CVE-2026-61477 -

1. Earlier the AI patch was correct as it was applying 3 patches from upstream, which are needed to fix this CVE.
   Kindly refer following Debian link - https://security-tracker.debian.org/tracker/CVE-2026-61477.
   It has shared 4 upstream patch links for this CVE. We can ignore 4th one as it is having only test files, if they are not present in our current source.
2. Once reverted back, the AI patch will completely match with upstream patch.

CVE-2026-63622 & CVE-2026-63623 -

1. The AI patches for both the CVEs completely match with respective upstream patches.
2. AI Patches have correct upstream patch references.

Kindly revert back the CVE-2026-61477 patch, as the AI patch was correct and re-trigger buddy build.

[durgajagadeesh]

Buddy build:

[Kanishk Bansal (Kanishk-Bansal)]

/azurepipelines run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.

[Kanishk Bansal (Kanishk-Bansal)]

/azurepipelines run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.