CVE-2024-8612: QEMU · Flaw Was Found
Affects qemuSource GCVE Database
Not known to be exploited · CVSS 3.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu:Pro:14.04:LTSqemupkg:deb/ubuntu/qemu?arch=source&distro=esm-infra-legacy/trustyOther threats | Affected
| Fixed in– |
Ubuntu:Pro:16.04:LTSqemupkg:deb/ubuntu/qemu?arch=source&distro=esm-infra-legacy/xenialOther threats | Affected
| Fixed in– |
Ubuntu:Pro:18.04:LTSqemupkg:deb/ubuntu/qemu?arch=source&distro=esm-infra/bionicOther threats | Affected
| Fixed in– |
Ubuntu:Pro:20.04:LTSqemupkg:deb/ubuntu/qemu?arch=source&distro=esm-infra/focalOther threats | Affected
| Fixed in– |
Ubuntu:22.04:LTSqemupkg:deb/ubuntu/qemu?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu:24.04:LTSqemupkg:deb/ubuntu/qemu?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu:25.10qemupkg:deb/ubuntu/qemu?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu:26.04:LTSqemupkg:deb/ubuntu/qemu?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.