[Medium] Patch kubevirt for CVE-2024-33394

[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 kubevirt for CVE-2024-33394
Patch Modified: Yes

• Patch was backported for manifests/generated/operator-csv.yaml.in and manifests/generated/rbac-operator.authorization.k8s.yaml.in due to version mismatch between existing "kubevirt" and "Astrolabe Patch".
• Astrolabe Patch Reference: kubevirt/kubevirt@772bb22

Change Log

• new: SPECS/kubevirt/CVE-2024-33394
• modified: SPECS/kubevirt/kubevirt.spec

Does this affect the toolchain?

NO

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2024-33394

Test Methodology

• Local build
• Patch applies cleanly

• Build is successful -
  kubevirt-0.59.0-29.cm2.src.rpm.log

[mfrw]

Triggered Test Build.
Reviewing patch meanwhile.

[mfrw]

Test Build Triggered: link