Host process crash via SDHCI off-by-one access
Published Nov 7, 2022 · Updated May 5, 2025
Off-by-one access in QEMU 7.1.0-rc4 and earlier allows guest OS users to crash the host process through the emulated SDHCI device. When data_count equals block_size, sdhci_read_dataport and sdhci_write_dataport perform an extra Buffer Data Port access beyond the configured block. Exploitation requires control of a guest with the emulated SDHCI controller and interrupts its QEMU host process without reported disclosure or code execution.
Summary
What happened
Off-by-one access in QEMU 7.1.0-rc4 and earlier allows guest OS users to crash the host process through the emulated SDHCI device. When data_count equals block_size, sdhci_read_dataport and sdhci_write_dataport perform an extra Buffer Data Port access beyond the configured block. Exploitation requires control of a guest with the emulated SDHCI controller and interrupts its QEMU host process without reported disclosure or code execution.
The record
- CVE
- CVE-2022-3872
- Published
- Nov 7, 2022
- Updated
- May 5, 2025
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-193, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 7, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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=Affected: up to latest v7.1.0-rc4
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