CVE-2024-3447: Qemu: sdhci: heap buffer overflow in sdhci_write_dataport()
A heap-based buffer overflow was found in the SDHCI device emulation of QEMU. The bug is triggered when both `s->data_count` and the size of `s->fifo_buffer` are set to 0x200, leading to an out-of-bound access. A malicious guest could use this flaw to crash the QEMU process on the host, resulting in a denial of service condition.
Security readout for executives and security teams
Plain-English summary
This QEMU flaw lets a highly privileged local guest crash the host-side QEMU process by hitting a bug in SDHCI device emulation. The expected business impact is VM denial of service, not data theft or host takeover based on the supplied sources. Treat it as a virtualization availability risk, especially where untrusted tenants run guests.
Executive priority
Prioritize normal patch-cycle remediation unless the environment hosts untrusted or tenant-controlled VMs. In multi-tenant virtualization, raise priority because a guest-triggered QEMU crash can interrupt workloads and service availability. Current supplied evidence does not justify emergency treatment as a known exploited vulnerability.
Technical view
CVE-2024-3447 is a CWE-122 heap buffer overflow in QEMU SDHCI emulation. The source describes out-of-bounds access when internal data and FIFO sizes reach 0x200. CVSS 3.1 is 6.0 with local attack vector, high privileges required, changed scope, and high availability impact.
Likely exposure
Exposure is most relevant to QEMU/KVM virtualization hosts that present SDHCI emulated devices to guests. The supplied Red Hat entries mark listed RHEL packages as unaffected, but other vendor advisories exist. Confirm exposure by distribution, appliance, and QEMU build rather than assuming all QEMU deployments are affected.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. The described attacker is a malicious local guest with high privileges. Public references include OSS-Fuzz and QEMU patch discussion, indicating discoverability, but the provided evidence supports denial of service rather than confidentiality or integrity compromise.
Researcher notes
Key constraints are local attack vector and high guest privileges. The affected-data section is inconsistent: it lists QEMU 1.5.0 and several Red Hat package lines marked unaffected. Use vendor package status and the upstream QEMU patch reference for precise exposure decisions; do not infer fixed versions from this bundle alone.
Mitigation direction
Check vendor advisories for your QEMU, appliance, or distribution build.
Apply vendor-provided QEMU updates when available for your platform.
Disable SDHCI emulation where it is not required.
Limit privileged access inside guest VMs, especially for untrusted tenants.
Monitor for unexplained QEMU process crashes tied to guest activity.
Validation and detection
Inventory virtualization hosts and identify QEMU/KVM versions and packages.
Review VM hardware configuration for SDHCI emulated devices.
Confirm vendor status against Red Hat, Debian, NetApp, and Siemens advisories.
Verify patched builds include the QEMU SDHCI bounds fix.
Check host logs for QEMU crashes or VM availability incidents.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.