8000 Update cloud-hypervisor to 54.1 by gominimal-pkgmgr-mgr[bot] · Pull Request #1450 · gominimal/pkgs · GitHub
[go: up one dir, main page]

Skip to content

Update cloud-hypervisor to 54.1 - #1450

Queued
gominimal-pkgmgr-mgr[bot] wants to merge 1 commit into
mainfrom
update-cloud-hypervisor-54.1
Queued

gominimal-pkgmgr-mgr[bot] wants to merge 1 commit into
mainfrom
update-cloud-hypervisor-54.1

Conversation

@gominimal-pkgmgr-mgr
Copy link
Copy Markdown
Contributor

Update cloud-hypervisor 54.0 → 54.1

Source: github:cloud-hypervisor/cloud-hypervisor:operator-pinned
Release: https://github.com/cloud-hypervisor/cloud-hypervisor/releases/tag/v54.1
Changelog: cloud-hypervisor/cloud-hypervisor@v54.0...v54.1
Released: 18 hours ago (2026-11-11)

Carried patches vs 54.1

Each | Local patch was dry-run against the extracted 54.1 tree, forward and reverse, both with exact context (patch -N -F0, patch -R -F0). Only a patch that reverse-applies WHOLE is treated as upstream; a partial match is a conflict, and one that applies forward only with fuzz is reported as such.

  • Regenerated security-floors-lock.patch — a pkgmgr lock-patch patch, re-resolved with cargo against 54.1's own lock (cargo metadata --locked verified) with its build.sh block: floors rustix 1.1.5 → 1.1.6 (RUSTSEC-2026-0486).

License

  • Upstream 54.0 → 54.1: couldn't determine: neither release has a LICENSE/COPYING file the scanner recognizes
  • Declared license_spdx: Apache-2.0 AND BSD-3-Clause, not checked against upstream: the new release has no LICENSE/COPYING file the scanner recognizes

Pkgscan: clean — diff against the prior version surfaced no newly-introduced suspicious patterns.

Vulnerability impact

Partition analysis at 54.1 (uses each advisory's fixed-version, vulnerable-range, affected-ranges, and fix-commit ancestry to decide):

  • 1 cleared — the new version is outside the advisory's affected range, OR the tag's lineage includes a known fix-commit. These will drop off the next scan.

Vulnerabilities fixed (1)

This update clears 1 vulnerabilities affecting 54.0:

CVE / GHSA CPE Severity Fixed in
GHSA-3r3x-6hgg-2m38 (cloudhypervisor, cloud_hypervisor) HIGH via range: <= 54.0
Advisory summaries
  • GHSA-3r3x-6hgg-2m38 — Use-after-free in virtio-pmem during VM shutdown (Published 2026-11-11)

Components changed

CycloneDX component delta (declared materials — the package's own version, not a dependency-tree diff)
Component Old New
~ cloud-hypervisor 54.0 54.1
~ cloud-hypervisor-upstream 54.0 54.1

Changes

Old New
Version 54.0 54.1
SHA256 000b1194ce4fcc05... 766e91fc0f6be59b...
Size 1.7 MB
Source https://github.com/cloud-hypervisor/cloud-hypervisor/archive/refs/tags/v54.0.tar.gz https://github.com/cloud-hypervisor/cloud-hypervisor/archive/refs/tags/v54.1.tar.gz

🔒 TLS: github.com — Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (root c90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519 ⇒ codeload.github.com — Sectigo Public Server Authentication CA DV E36 → Sectigo Public Server Authentication Root E46 (root c90f26f0fb1b4018…) · TLSv1_3 · TLS13_AES_128_GCM_SHA256 · X25519


Created by pkgmgr

@gominimal-pkgmgr-mgr
gominimal-pkgmgr-mgr Bot requested a review from a team as a code owner November 11, 2026 19:24
@coderabbitai
coderabbitai Bot commented Nov 11, 2026
Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@bryan-minimal
bryan-minimal added this pull request to the merge queue Nov 12, 2026
Any commits made after this event will not be merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0