A bug in QEMU could cause a guest I/O operation otherwise addressed to an arbitrary disk offset to be targeted to offset 0 instead (potentially overwriting the VM's boot code). This could be used, for example, by L2 guests with a virtual disk (vdiskL2) stored on a virtual disk of an L1 (vdiskL1) hypervisor to read and/or write data to LBA 0 of vdiskL1, potentially gaining control of L1 at its next reboot.
References
| Link | Resource |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=2247283 | Issue Tracking Patch |
| https://access.redhat.com/security/cve/CVE-2023-5088 | Third Party Advisory |
| https://lore.kernel.org/all/20230921160712.99521-1-simon.rowe@nutanix.com/T/ | Mailing List Patch |
| https://security.netapp.com/advisory/ntap-20231208-0005/ |
Information
Published : 2023-11-03 14:15
Updated : 2023-12-08 19:15
NVD link : CVE-2023-5088
Mitre link : CVE-2023-5088
JSON object : View
Products Affected
redhat
- enterprise_linux
qemu
- qemu
CWE
CWE-662
Improper Synchronization
