Skip to content
Fencer Vulns
low 3.8

CVE-2024-8612 json

Qemu-kvm: information leak in virtio devices

published 2024-09-20 2 y ago modified 2026-11-06 2 d ago also EUVD-2024-49297

cvss
3.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

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.

Patch / fix

  • qemu SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Micro 5.2 +3 more 5.2.0-150300.135.1
  • qemu Linux Micro 6.0 8.2.7-1.1
  • qemu SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Micro 5.4 +5 more 6.2.0-150400.37.37.3
  • qemu SLE Module for Server Applications 15 SP6, SLE Module for Package Hub 15 SP6, SLE Module for Basesystem 15 SP6 +1 more 8.2.7-150600.3.20.1
  • qemu-linux-user SLE Module for Package Hub 15 SP6, openSUSE Leap 15.6 8.2.7-150600.3.20.1
  • qemu SLE Module for Server Applications 15 SP5, SLE Module for Package Hub 15 SP5, SLE Module for Basesystem 15 SP5 +3 more 7.1.0-150500.49.24.1
  • qemu SLE Module for Confidential Computing Technical Preview 15 SP6 8.2.7-15061.6.coco15sp6.1

suse advisories SUSE-SU-2025:0692-1SUSE-SU-2025:20076-1SUSE-SU-2024:4304-1SUSE-SU-2024:4094-1SUSE-SU-2024:3948-1SUSE-SU-2024:3744-1

  • qemu openSUSE Tumbleweed 9.1.0-2.1

opensuse advisories openSUSE-SU-2024:14411-1

  • qemu Azure Linux 3.0 9.1.0-1

azure linux advisories AZL-60910

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-8612 updated cvss 3.8

qemu-kvm: information leak in virtio devices

  • Red Hat Enterprise Linux 6 qemu-img, qemu-kvm, qemu-kvm-tools, qemu-guest-agent, qemu-guest-agent-win32 Red Hat Enterprise Linux 7 qemu-img, qemu-kvm, libcacard, qemu-img-ma, qemu-kvm-ma, qemu-kvm-tools, +5 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 qemu-img, qemu-kvm, qemu-kvm-core, qemu-kvm-tests, qemu-kvm-common, qemu-guest-agent, +8 more Red Hat Enterprise Linux 8 Advanced Virtualization qemu-img, qemu-kvm, qemu-kiwi, qemu-kvm-core, qemu-kvm-tests, qemu-kvm-common, +9 more Red Hat Enterprise Linux 9 qemu-img, qemu-kvm, qemu-kvm-core, qemu-kvm-tools, qemu-pr-helper, qemu-kvm-common, +16 more Red Hat Enterprise Linux 10 qemu-kvm
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Affected products

  • Red Hat Red Hat Enterprise Linux 10
  • Red Hat Red Hat Enterprise Linux 6
  • Red Hat Red Hat Enterprise Linux 7
  • Red Hat Red Hat Enterprise Linux 8
  • Red Hat Red Hat Enterprise Linux 8 Advanced Virtualization
  • Red Hat Red Hat Enterprise Linux 9

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.