CVE-2025-54567
Qemu ≤ 10.0.3
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LSummary
CVE-2025-54567 is a medium-severity Incorrect Provision of Specified Functionality (CWE-684) vulnerability in Qemu Qemu. Its CVSS base score is 4.2 (Medium).
Operationally, ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and CM-7 (Least Functionality) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-22565
Vulnerability Data
hw/pci/pcie_sriov.c in QEMU through 10.0.3 mishandles the VF Enable bit write mask, a related issue to CVE-2024-26327.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires timely patching of the VF Enable bit write-mask flaw in QEMU's SR-IOV implementation.
Disables or restricts the PCI SR-IOV feature (and VF Enable) when not required, eliminating the attack surface.
Enforces process isolation so a compromised QEMU SR-IOV path cannot affect other VM or host components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce spec-compliant functionality and testing, while eliminating this weakness fulfills only part of the control's broader monitoring intent.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance validates that implemented functionality conforms to specifications before release.
Secure development life cycle includes requirements and verification activities that directly reduce the risk of delivering functionality that deviates from published specifications.
Explicit application security requirements and acceptance criteria help ensure the delivered software matches its intended specifications.
Change management processes reduce the chance of unintended functional deviations during updates, though they do not directly address initial specification conformance.