Qemu: Heap-buffer-overflow in sdhci_write
A heap-buffer-overflow vulnerability exists in the sdhci_write function of QEMU, as reported by OSS-Fuzz. This issue involves a write operation that exceeds the allocated heap buffer, potentially leading to memory corruption. The vulnerability affects multiple specific versions of QEMU from 7.0.0 through 11.1.0-rc2 and beyond a certain commit. No CVSS score is provided, but the severity is assessed as high due to the nature of heap-buffer-overflow flaws.
AI Analysis
Technical Summary
The vulnerability is a heap-buffer-overflow in the sdhci_write function within QEMU, identified by OSS-Fuzz. The crash involves a write operation that overflows a heap buffer, as indicated by the crash state involving sdhci_write, memory_region_write_accessor, and memory_region_dispatch_write. This flaw affects a wide range of QEMU versions starting from 7.0.0 and including various release candidates and stable releases up to at least 11.1.0-rc2, as well as versions after a specific commit (>=b7a3a705b644495b7b578e94e0e9dedf93c4f661). The vulnerability could lead to memory corruption within the QEMU process.
Potential Impact
Heap-buffer-overflow vulnerabilities can cause memory corruption, which may lead to crashes or potentially enable code execution within the QEMU process. This can affect the stability and security of virtual machines running under QEMU. No known exploits in the wild have been reported for this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official patch links are provided in the available data. Users should monitor QEMU vendor advisories and OSS-Fuzz reports for updates and apply patches once available.
Qemu: Heap-buffer-overflow in sdhci_write
Description
A heap-buffer-overflow vulnerability exists in the sdhci_write function of QEMU, as reported by OSS-Fuzz. This issue involves a write operation that exceeds the allocated heap buffer, potentially leading to memory corruption. The vulnerability affects multiple specific versions of QEMU from 7.0.0 through 11.1.0-rc2 and beyond a certain commit. No CVSS score is provided, but the severity is assessed as high due to the nature of heap-buffer-overflow flaws.
Affected software
pkg:generic/qemuRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability is a heap-buffer-overflow in the sdhci_write function within QEMU, identified by OSS-Fuzz. The crash involves a write operation that overflows a heap buffer, as indicated by the crash state involving sdhci_write, memory_region_write_accessor, and memory_region_dispatch_write. This flaw affects a wide range of QEMU versions starting from 7.0.0 and including various release candidates and stable releases up to at least 11.1.0-rc2, as well as versions after a specific commit (>=b7a3a705b644495b7b578e94e0e9dedf93c4f661). The vulnerability could lead to memory corruption within the QEMU process.
Potential Impact
Heap-buffer-overflow vulnerabilities can cause memory corruption, which may lead to crashes or potentially enable code execution within the QEMU process. This can affect the stability and security of virtual machines running under QEMU. No known exploits in the wild have been reported for this vulnerability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official patch links are provided in the available data. Users should monitor QEMU vendor advisories and OSS-Fuzz reports for updates and apply patches once available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- OSV-2023-390
- Osv Schema Version
- 1.4.0
- Ecosystems
- ["OSS-Fuzz"]
Threat ID: 6a6ae55f9c2644c7f89b09e6
Added to database: 07/30/2026, 05:47:11 UTC
Last enriched: 08/14/2026, 19:18:40 UTC
Last updated: 09/07/2026, 17:33:43 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.