[AutoPR- Security] Patch qemu for CVE-2026-3196 [MEDIUM]

[azurelinux-security]

Auto Patch qemu for CVE-2026-3196.

Autosec pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=1150719&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 qemu for CVE-2026-3196 (MEDIUM).

Change Log

• CVE-2026-3196

Does this affect the toolchain?

YES/NO

Associated issues

• N/A

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-2026-3196

Test Methodology

• Pipeline build id: Buddy Build URL

[AkarshHCL]

1. Patch is in sync with upstream patch.
2. Buddy build is successful with patch getting applied-

3. Tried local build by adding some error in the affected file build fails due to introduced error.

[mfrw]

LGTM ✅ — faithful backport of the upstream fix, spec hygiene clean, and the buddy build is green on both arches including qemu's %check.

Patch fidelity — ✅ matches upstream

SPECS/qemu/CVE-2026-3196.patch is byte-for-byte identical (modulo expected base drift) to upstream qemu d84fbf24 (cherry-picked from 61679d7, by Manos Pitsidianakis, Reviewed-by: mst) — the fix for VIRTIO spec §5.14.6.2 in virtio_snd_handle_pcm_info:

• both added guards match exactly: the start_id + count > s->snd_conf.streams bounds check, and the g_uint_checked_mul/g_uint_checked_add overflow-guarded buffer-size check;
• the only deltas vs upstream are the hunk offsets (181/207 vs 156/179) and blob hashes — expected because the base is qemu 9.1.0, not upstream HEAD;
• the preserved /* TODO: do we need to set DEVICE_NEEDS_RESET? */ context comment exists in the 9.1.0 base and is untouched — benign.

Spec hygiene — ✅ clean

• Release: 9 → 10
• Patch33: CVE-2026-3196.patch declared in correct sequential order after Patch32
• %changelog entry for 9.1.0-10 present and correct (date/author/CVE)
• No source tarball change → no *.signatures.json update needed

Build / CI — buddy build buildId=1151905 (Run 20260702.3) — 237 succeeded / 10 skipped / 0 failed

Stage	AMD64	ARM64
Build qemu-9.1.0-10.azl3 RPMs	✅ succeeded	✅ succeeded
%check (package test)	✅ EXIT STATUS 0 → Pass (631s)	✅ EXIT STATUS 0 → Pass (445s)
Sodiff check (ABI/.so diff)	✅ succeeded	✅ succeeded
Toolchain build + postBuild	✅ succeeded	✅ succeeded
sdl_sources	✅ succeeded	—

All GitHub PR checks green; merge checklist ticked in the PR body.

Non-blocking note

tmp is only ever written (as the output arg of the g_uint_checked_* helpers) and never read — its sole purpose is overflow detection via short-circuit, and the final comparison recomputes sizeof(virtio_snd_hdr) + size * count. This is intentional and identical to upstream; no -Wunused-but-set-variable since it's passed by address and the build is warning-clean. Just flagging for completeness.

Signed-Off By: @mfrw

[kgodara912]

Patch matches with upstream reference. Buddy build is successful. LGTM.