Vulnerability Description
A flaw was found in QEMU, in the virtio-scsi, virtio-blk, and virtio-crypto devices. The size for virtqueue_push as set in virtio_scsi_complete_req / virtio_blk_req_complete / virito_crypto_req_complete could be larger than the true size of the data which has been sent to guest. Once virtqueue_push() finally calls dma_memory_unmap to ummap the in_iov, it may call the address_space_write function to write back the data. Some uninitialized data may exist in the bounce.buffer, leading to an information leak.
CVSS Score
LOW
Related Weaknesses (CWE)
References
- https://access.redhat.com/security/cve/CVE-2024-8612
- https://bugzilla.redhat.com/show_bug.cgi?id=2313760
- https://gitlab.com/qemu-project/qemu/-/commit/637b0aa139565cb82a7b9269e62214f870
- https://security.netapp.com/advisory/ntap-20241108-0006/
FAQ
What is CVE-2024-8612?
CVE-2024-8612 is a vulnerability with a CVSS score of 3.8 (LOW). A flaw was found in QEMU, in the virtio-scsi, virtio-blk, and virtio-crypto devices. The size for virtqueue_push as set in virtio_scsi_complete_req / virtio_blk_req_complete / virito_crypto_req_comple...
How severe is CVE-2024-8612?
CVE-2024-8612 has been rated LOW with a CVSS base score of 3.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-8612?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.