CVE-2024-3447

Qemu: sdhci: heap buffer overflow in sdhci_write_dataport()

MEDIUM
6
CVSS Score
Published: November 14, 2024 at 12:10 PM UTC
Updated: June 17, 2026 at 07:44 AM UTC
13 products affected across 3 vendorsQEMUHci Compute NodeRUGGEDCOM Rox RX1511 Firmware

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 7.2.118.0.0 ≤ v < 8.2.39.0.09.0.0 rc09.0.0 rc19.0.0 rc2
Affected range stops below 7.2.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.2.3, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement
v < V2.17.1
Affected range stops below V2.17.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (7)

VDB Entryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/security/cve/CVE-2024-3447
Issue Trackingx_refsource_REDHATThird Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=2274123
Vendor Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
https://security.netapp.com/advisory/ntap-20250425-0005/
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/04/msg00042.html
Source: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
https://cert-portal.siemens.com/productcert/html/ssa-577017.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6MEDIUMfedora
Attack Vector
LOCAL
Complexity
LOW
Privileges
HIGH
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-122

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card