1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Okay, I need to classify this bug report from QEMU into one of the given categories. Let's see what the problem is about.
The title says "Crash in pc_system_parse_ovmf_flash caused by bad firmware file." So it's related to parsing an OVMF flash file. The description mentions a crash due to an out-of-bounds read in memcpy() because there's no check on the tot_len field from the flash file, leading to ptr - tot_len pointing below flash_ptr.
Looking at the steps to reproduce, it involves creating a specially-crafted flash file with a bad tot_len value. Then, starting QEMU with SEV (which requires KVM and x86_64). The crash happens when running this setup.
The categories I have are: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
Since the issue is in pc_system_parse_ovmf_flash and it's related to SEV (which uses KVM), but more specifically, it's about how QEMU handles a malformed firmware file. The bug occurs during the parsing of the OVMF flash file, which is part of the system firmware initialization.
This doesn't seem to be related to translation or assembly lowering. It's also not directly under device, graphic, network, etc., because it's more about how QEMU initializes and parses the firmware data, leading to a crash when an invalid file is provided.
Since SEV is enabled through KVM, but the root cause isn't in the hypervisor code itself but rather in the handling of the firmware file during system initialization. Therefore, the category that best fits this bug is 'files' because it's about reading and processing a file (the OVMF flash file) incorrectly.
</think>
files
|