Guest-triggered emulator crash via unchecked NumVFs
Published Feb 19, 2024 · Updated Aug 2, 2024
Heap buffer overflow in QEMU 7.1.0 through 8.2.1 allows guest OS users to crash the emulator by setting an excessive SR-IOV NumVFs value. The register_vfs function in hw/pci/pcie_sriov.c uses guest-controlled NumVFs without rejecting values above TotalVFs, overrunning VF storage. The guest must access an emulated SR-IOV physical function and enable its virtual functions; the resulting memory corruption terminates the QEMU process and interrupts the VM.
Summary
What happened
Heap buffer overflow in QEMU 7.1.0 through 8.2.1 allows guest OS users to crash the emulator by setting an excessive SR-IOV NumVFs value. The register_vfs function in hw/pci/pcie_sriov.c uses guest-controlled NumVFs without rejecting values above TotalVFs, overrunning VF storage. The guest must access an emulated SR-IOV physical function and enable its virtual functions; the resulting memory corruption terminates the QEMU process and interrupts the VM.
The record
- CVE
- CVE-2024-26327
- Published
- Feb 19, 2024
- Updated
- Aug 2, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-122, CWE-787, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=-
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