# CVE-2025-12464: Qemu-kvm: stack buffer overflow in e1000 device via short frames in loopback mode

> A malicious guest user can crash the QEMU host process via a stack buffer overflow in the e1000 network device loopback mode.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Oct 2025
- **Updated:** 31 Aug 2026
- **Also known as:** AZL-69631, BELL-CVE-2025-12464, DEBIAN-CVE-2025-12464, GHSA-59fq-gggw-pqjr, UBUNTU-CVE-2025-12464

## What is CVE-2025-12464?

CVE-2025-12464 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 31 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-based buffer overflow was found in the QEMU e1000 network device. The code for padding short frames was dropped from individual network devices and moved to the net core code. The issue stems from the device's receive code still being able to process a short frame in loopback mode. This could lead to a buffer overrun in the e1000_receive_iov() function via the loopback code path. A malicious guest user could use this vulnerability to crash the QEMU process on the host, resulting in a denial of service.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-12464?


## How do I fix CVE-2025-12464?

Apply the vendor's patch.

## Is CVE-2025-12464 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12464 and fix it if it is affected.

What it is: CVE-2025-12464 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 31 Oct 2025. 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-2025-12464 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-2025-12464/ (Markdown: https://insights.sbomify.com/CVE-2025-12464/index.md)
```

## Sources

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

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