CVE-2024-8612: Qemu-kvm: information leak in virtio devices

Published Sep 20, 2024
·
Updated

A flaw was found in QEMU in the virtio-scsi, virtio-blk and virtio-crypto devices. The size for virtqueuepush as set in virtioscsicompletereq / virtioblkreqcomplete / viritocryptoreqcomplete could be larger than the true size of the data which has been sent to guest.

Once virtqueuepush() finally calls dmamemoryunmap to ummap the iniov, it may call the addressspacewrite function to write back the data. Some uninitialized data may exist in the bounce.buffer, leading to an information leak.

Upstream fix: https://gitlab.com/qemu-project/qemu/-/commit/637b0aa139565cb82a7b9269e62214f87082635c

Other sources

A flaw was found in QEMU, in the virtio-scsi, virtio-blk, and virtio-crypto devices. The size for virtqueuepush as set in virtioscsicompletereq / virtioblkreqcomplete / viritocryptoreqcomplete could be larger than the true size of the data which has been sent to guest. Once virtqueuepush() finally calls dmamemoryunmap to ummap the iniov, it may call the addressspacewrite function to write back the data. Some uninitialized data may exist in the bounce.buffer, leading to an information leak.

NVD

Qemu-kvm: information leak in virtio devices

Microsoft

Affected Software

7 affected componentsFixes available
Qemu Qemu
Microsoft azl3 qemu 8.2.0-25
Microsoft azl3 qemu 8.2.0-27<9.1.0-1
9.1.0-1
Microsoft azl3 qemu 8.2.0-19
Microsoft cbl2 qemu 6.2.0-26
Microsoft cbl2 qemu 6.2.0-25
Microsoft azl3 qemu 8.2.0-17

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 9.1.0-1

Event History

Sep 20, 2024
Data Sourced
via Red Hat·01:04 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·05:50 PM
Data Sourced
via MITRE·05:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Sep 4, 2025
Data Sourced
via Microsoft·05:21 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·05:21 AM
SeverityAffected Software
Updated
via Microsoft·05:21 AM
Affected Software
Updated
via Microsoft·12:21 PM
Affected Software
Updated
via Microsoft·12:21 PM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-8612?

CVE-2024-8612 has been classified as a medium severity vulnerability due to potential data corruption issues.

2

How do I fix CVE-2024-8612?

To mitigate CVE-2024-8612, update your QEMU installation to the latest version where the vulnerability is addressed.

3

What components are affected by CVE-2024-8612?

CVE-2024-8612 affects the virtio-scsi, virtio-blk, and virtio-crypto devices within QEMU.

4

What is the impact of CVE-2024-8612 on system security?

The impact of CVE-2024-8612 may include potential data corruption when processing requests within virtualized environments.

5

Is CVE-2024-8612 present in all QEMU versions?

CVE-2024-8612 is found in specific versions of QEMU, so users should review their version against security advisories to determine exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203