Repository navigation
fix(vmm): ship cloud hypervisor 51.2 and drop vulnerable builds - #585
Open
walsykerem wants to merge 3 commits into
Open
walsykerem wants to merge 3 commits into
walsykerem wants to merge 3 commits into
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit bcf7edc. Configure here.
… dropped A cold start of a stopped instance replays the hypervisor version pinned in its metadata. Dropping v51.1 and v49.0 left those instances failing with 'unsupported cloud-hypervisor version: v51.1' before the VMM was even spawned, because cloud-hypervisor does not refresh the host version on start. Resolve the stored version through the starter and fall back to the starter default when it can no longer be resolved, logging a warning and persisting the new version. Snapshot restores keep using the pinned version and still fail loudly.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Cloud Hypervisor is the VMM behind Hypeman's Linux guests, and the project shipped v51.1 as its default while still offering v49.0 as a selectable version. Both fall inside the affected range of CVE-2026-45782, a guest triggered use after free in the virtio block async completion path rated 8.9, and v49.0 also sits below the fix for CVE-2026-27211. Creating an instance with an explicit hypervisor version was enough to reach either one.
The fix moves every reference to v51.2, the first release carrying the patch: the embedded binary declarations, the default and supported version lists, the capability switch, the download targets, the CI download loop, and the OpenAPI spec URL. v49.0 is dropped entirely, so the supported set is one safe version. Standby instances recorded on a removed version have to be shut down and recreated, and the vmm README says so. Tests that referenced the old constants moved to the new one, and the capability check still proves that a legacy v49.0 instance does not advertise live disk resize.
The binary audit script passes now and fails on the original tree.
Note
Medium Risk
Removes older VMM binaries (breaking exact-version snapshot restore for standby instances on dropped builds) while adding default-version fallback on cold start; otherwise a focused security and packaging upgrade.
Overview
Upgrades the embedded Cloud Hypervisor default and supported set to v51.2, removing v49.0 and v51.1 everywhere binaries, OpenAPI spec sources, CI downloads, and capability wiring are defined (CVE-2026-45782 is noted as the driver in the Makefile/vmm docs).
Cold starts of stopped instances whose metadata still pin a dropped version no longer fail permanently:
resolveStartVersioninstartAndBootVMretries with the starter’s default version, logs a warning, and updates stored metadata—covered by new unit/integration-style tests.Tests, READMEs, and registry expectations are aligned with a single shipped CH build; legacy v49.0 capability behavior (no live disk resize) is still asserted for restored/metadata-driven paths where applicable.
Reviewed by Cursor Bugbot for commit 83546ea. Bugbot is set up for automated code reviews on this repo. Configure here.