CVE-2025-54566
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedhw/pci/pcie_sriov.c in QEMU through 10.0.3 has a migration state inconsistency, a related issue to CVE-2024-26327.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceQEMU's PCIe SR-IOV (Single Root I/O Virtualization) implementation in hw/pci/pcie_sriov.c contains a migration state inconsistency that can cause issues when migrating virtual machines with SR-IOV virtual functions. This is a related issue to CVE-2024-26327, another migration-related vulnerability in QEMU. The vulnerability allows a potentially malicious or buggy VM to affect migration integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed QEMU versionRun `qemu --version` or check via package manager (e.g., `dpkg -l qemu-system-x86`, `rpm -q qemu-kvm`)Affected if The installed version is 10.0.3 or lower
-
Verify SR-IOV capability in QEMU binaryCheck if the QEMU binary supports SR-IOV by searching for pcie_sriov in the binary or checking compile-time options: `strings /path/to/qemu-system-x86_64 | grep -i sriov`Affected if SR-IOV support is compiled into the QEMU binary
-
Identify configured virtual functionsList SR-IOV virtual functions on the host using `lspci -vvv | grep -i 'Virtual Function'` or check sysfs: `ls /sys/bus/pci/devices/*/virtfn*`Affected if Any virtual functions are configured on the host
-
Identify VMs with SR-IOV devices attachedFor each VM, inspect configuration (e.g., via libvirt: `virsh dumpxml vmname` or QEMU args) to check for SR-IOV VF devices assignedAffected if Any VMs have SR-IOV virtual functions assigned to them
A user is affected if their QEMU version is 10.0.3 or lower AND they have SR-IOV virtual functions configured on the host that could be migrated.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade QEMU to a version beyond 10.0.3 that addresses this vulnerability. Until patched, avoid migrating virtual machines that have SR-IOV virtual functions configured, or ensure the source and destination QEMU instances are at the same patched version.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54566 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54566 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data