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.
Weakness
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Qemu |
Qemu |
* |
7.2.11 (excluding) |
| Qemu |
Qemu |
8.0.0 (including) |
8.2.3 (excluding) |
| Qemu |
Qemu |
9.0.0 (including) |
9.0.0 (including) |
| Qemu |
Qemu |
9.0.0-rc0 (including) |
9.0.0-rc0 (including) |
| Qemu |
Qemu |
9.0.0-rc1 (including) |
9.0.0-rc1 (including) |
| Qemu |
Qemu |
9.0.0-rc2 (including) |
9.0.0-rc2 (including) |
| Qemu |
Ubuntu |
devel |
* |
| Qemu |
Ubuntu |
focal |
* |
| Qemu |
Ubuntu |
jammy |
* |
| Qemu |
Ubuntu |
mantic |
* |
| Qemu |
Ubuntu |
noble |
* |
| Qemu |
Ubuntu |
oracular |
* |
| Qemu |
Ubuntu |
plucky |
* |
| Qemu |
Ubuntu |
questing |
* |
| Qemu |
Ubuntu |
trusty/esm |
* |
| Qemu |
Ubuntu |
upstream |
* |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
References