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

> A flaw in QEMU virtio devices allows attackers to leak uninitialized memory data to the guest, potentially exposing sensitive information.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Sep 2024
- **Updated:** 8 Nov 2025
- **Also known as:** AZL-60151, AZL-60910, DEBIAN-CVE-2024-8612, ECHO-0fa5-4d4e-1a97, GHSA-whq8-5442-qhw7, OESA-2024-2267, UBUNTU-CVE-2024-8612

## What is CVE-2024-8612?

CVE-2024-8612 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-8612?


## How do I fix CVE-2024-8612?

Apply the vendor's patch.

## Is CVE-2024-8612 being exploited?

There is no known exploitation of CVE-2024-8612 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8612 and fix it if it is affected.

What it is: CVE-2024-8612 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 20 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8612 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8612/ (Markdown: https://insights.sbomify.com/CVE-2024-8612/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8612
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8612
- OSV: https://osv.dev/vulnerability/CVE-2024-8612

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8612/
Summaries are generated and may contain mistakes; the official description above is the record.