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->datacount and the size of s->fifobuffer 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.
Upstream patch: https://patchew.org/QEMU/20240404085549.16987-1-philmd@linaro.org/
oss-fuzz bug: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58813
Other sources
A heap-based buffer overflow was found in the SDHCI device emulation of QEMU. The bug is triggered when both s->datacount and the size of s->fifobuffer 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.
— MITRE
Qemu: sdhci: heap buffer overflow in sdhciwritedataport()
— Microsoft
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-3447?
CVE-2024-3447 is classified as a critical vulnerability due to the potential for a heap-based buffer overflow leading to crashes.
How do I fix CVE-2024-3447?
To mitigate CVE-2024-3447, update to the latest version of QEMU that addresses this vulnerability.
What causes CVE-2024-3447?
CVE-2024-3447 is triggered when both 's->data_count' and the size of 's->fifo_buffer' are incorrectly set, leading to out-of-bounds access.
Who is impacted by CVE-2024-3447?
Any system using vulnerable versions of QEMU may be impacted by CVE-2024-3447, especially if it processes untrusted guest data.
What are the consequences of exploiting CVE-2024-3447?
Exploitation of CVE-2024-3447 can lead to a crash of the QEMU process, resulting in denial of service.