dbcve.org
QemuApplication

CVE-2024-26328

MEDIUM · 6.0 CVSS v3.1 Published 2024-02-19
Fix available
A fix is available. Upgrade to after 8.2.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Zero-click

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 · unedited
An issue was discovered in QEMU 7.1.0 through 8.2.1. register_vfs in hw/pci/pcie_sriov.c does not set NumVFs to PCI_SRIOV_TOTAL_VF, and thus interaction with hw/nvme/ctrl.c is mishandled.

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 confidence

In QEMU 7.1.0 through 8.2.1, the register_vfs function in hw/pci/pcie_sriov.c fails to set the NumVFs field to PCI_SRIOV_TOTAL_VF when registering virtual functions. This causes incorrect interaction with the NVMe controller emulation in hw/nvme/ctrl.c, potentially leading to improper VF enumeration or configuration in SR-IOV-enabled virtual environments.

MitigationUpgrade QEMU to version 8.2.2 or later where the register_vfs function properly sets NumVFs to PCI_SRIOV_TOTAL_VF before interacting with NVMe controllers.

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
QemuApplication
Affected:>= 7.1.0, <= 8.2.1

CVSS 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed QEMU version
    Run 'qemu-system-x86_64 --version' or 'qemu-img --version' to determine the QEMU version number
    Affected if The version is >= 7.1.0 and <= 8.2.1
  2. Verify SR-IOV is enabled in the hypervisor
    Check for SR-IOV capability: on Linux, run 'lspci -vv' and look for 'SR-IOV' in the kernel driver, or check /sys/bus/pci/devices/*/sriov_numvfs
    Affected if SR-IOV is enabled and virtual functions (VFs) are being enumerated
  3. Confirm NVMe controller with SR-IOV is in use
    Check QEMU command line or libvirt XML for an NVMe device with SR-IOV configuration, such as a PCIe NVMe controller with 'x-sriov=on' or a VFs parameter
    Affected if An NVMe controller is being emulated with SR-IOV virtual functions configured
  4. Inspect pcie_sriov configuration for NumVFs mismatch
    Review the guest VM configuration or QEMU logs for errors related to VF enumeration; on the host, check 'lspci | grep -i nvme' to see if VFs appear with incorrect numbering
    Affected if Virtual functions are enumerated with incorrect or unexpected VF indices or counts

A system is affected if it runs QEMU 7.1.0-8.2.1 with an SR-IOV-enabled NVMe controller being emulated, and virtual function enumeration shows incorrect NumVFs values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.2.1
Interim mitigation

Upgrade QEMU to version 8.2.2 or later where the register_vfs function properly sets NumVFs to PCI_SRIOV_TOTAL_VF before interacting with NVMe controllers.

Recommended fix High confidence

QEMU 8.2.2 or later stable release

  1. 1. Identify the QEMU version currently installed (e.g., qemu-system-x86_64 --version)
  2. 2. Confirm the version is within the affected range: >= 7.1.0 and <= 8.2.1
  3. 3. Plan maintenance window for QEMU host reboot/management
  4. 4. Obtain the fixed QEMU version from official sources (e.g., https://www.qemu.org/download/)
  5. 5. Install the updated QEMU package using your system's package manager (apt, yum, dnf, etc.)
  6. 6. Verify the new version is installed and matches a fixed release (e.g., 8.2.2 or later)
  7. 7. Restart any QEMU instances or the QEMU daemon as needed
  8. 8. Re-verify that PCI SR-IOV functionality works correctly with the update
Caveat Minor: QEMU 8.2.x releases may have minor device emulation changes; test critical VM configurations before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qemu Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26328 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26328 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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