Virtual function state corruption via ignored write mask
Published Jul 25, 2025 · Updated Jul 25, 2025
Incorrect state management in QEMU 10.0.0 through 10.0.3 allows guest OS users to corrupt virtual-function state via PCIe SR-IOV writes. The pcie_sriov_config_write function treats its input value as already masked, so it processes VF Enable even when the configured write mask blocks that bit. Reachability requires guest access to an emulated SR-IOV physical function; crafted configuration writes cause incorrect virtual-function registration or removal.
Summary
What happened
Incorrect state management in QEMU 10.0.0 through 10.0.3 allows guest OS users to corrupt virtual-function state via PCIe SR-IOV writes. The pcie_sriov_config_write function treats its input value as already masked, so it processes VF Enable even when the configured write mask blocks that bit. Reachability requires guest access to an emulated SR-IOV physical function; crafted configuration writes cause incorrect virtual-function registration or removal.
The record
- CVE
- CVE-2025-54567
- Published
- Jul 25, 2025
- Updated
- Jul 25, 2025
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-684
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 25, 2025CVE publishedPublication date reported by the CVE source.
- Jul 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.0 <=10.0.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo