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.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:3948-1 advisory.

    - CVE-2024-8354: Fixed assertion failure in usb_ep_get() (bsc#1230834).
    - CVE-2024-8612: Fixed nformation leak in virtio devices (bsc#1230915).
    - CVE-2024-7409: Fixed denial of service via improper synchronization in QEMU NBD Server during socket     closure (bsc#1229007).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:3744-1 advisory.

    Security fixes:

    - CVE-2024-8354: Fixed assertion failure in usb_ep_get() (bsc#1230834)
    - CVE-2024-8612: Fixed information leak in virtio devices (bsc#1230915)

    Update version to 8.2.7:

    Security fixes:

    - CVE-2024-7409: Fixed denial of service via improper synchronization in QEMU NBD Server during socket     closure (bsc#1229007)
    - CVE-2024-4693: Fixed improper release of configure vector in virtio-pci that lead to guest triggerable     crash (bsc#1224132)

    Other fixes:

    - added missing fix for ppc64 emulation that caused corruption in userspace (bsc#1230140)
    - target/ppc: Fix lxvx/stxvx facility check (bsc#1229929)
    - accel/kvm: check for KVM_CAP_READONLY_MEM on VM (bsc#1231519)

    Full changelog here:

    https://lore.kernel.org/qemu-devel/d9ff276f-f1ba-4e90-8343-a7a0dc2bf305@tls.msk.ru/

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of QEMU installed on the remote Windows host is prior to 8.2.1 and therefore vulnerable to the following:
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. 

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
210712	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : qemu (SUSE-SU-2024:3948-1)	Nessus	SuSE Local Security Checks	low
209545	SUSE SLES15 Security Update : qemu (SUSE-SU-2024:3744-1)	Nessus	SuSE Local Security Checks	low
207835	QEMU 7.2.x < 7.2.15, 8.0.x < 8.0.6, 8.1.x < 8.1.6, 8.2.x < 8.2.8, 9.0.x < 9.0.4, 9.1.x < 9.1.1 Information Leak	Nessus	Windows	low

Detections

Analytics

CVE-2024-8612

low

Tenable Plugins

low

low

low