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://access.redhat.com/errata/RHSA-2024:2135 | |
https://access.redhat.com/errata/RHSA-2024:2962 | |
https://access.redhat.com/security/cve/CVE-2023-5088 | Third Party Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=2247283 | Issue Tracking Patch |
https://lists.debian.org/debian-lts-announce/2024/03/msg00012.html | |
https://lore.kernel.org/all/20230921160712.99521-1-simon.rowe@nutanix.com/T/ | Mailing List Patch |
https://security.netapp.com/advisory/ntap-20231208-0005/ | Third Party Advisory |
Configurations
History
No history.
Information
Published : 2023-11-03 14:15
Updated : 2024-05-22 17:16
NVD link : CVE-2023-5088
Mitre link : CVE-2023-5088
CVE.ORG link : CVE-2023-5088
JSON object : View
Products Affected
qemu
- qemu
redhat
- enterprise_linux