LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-12464 is a QEMU e1000 virtual network device flaw. A user inside a guest VM could trigger a stack buffer overflow in loopback handling and crash the QEMU process on the host. The stated impact is denial of service, not data theft or host takeover.

Executive priority

Treat as a medium-priority availability risk for affected virtualization platforms. It can disrupt workloads by crashing QEMU, but sources do not show active exploitation or confidentiality impact. Prioritize patch tracking and exposure inventory over emergency response unless critical services rely on affected hosts.

Technical view

The flaw is a CWE-121 stack-based buffer overflow in QEMU e1000 receive handling. Short-frame padding moved to net core, but e1000 loopback receive can still process short frames, overrunning e1000_receive_iov(). Red Hat rates it medium, CVSS 6.2, with availability impact only.

Likely exposure

Relevant to virtualization environments using affected qemu-kvm builds and e1000 virtual NICs. The source bundle lists Red Hat Enterprise Linux 9, Red Hat Enterprise Linux 10, and Red Hat OpenShift Container Platform 4 rhcos as affected. RHEL 6, 7, 8 entries are listed as unaffected.

Exploitation context

The attack is local to a guest VM context. Sources describe a malicious guest user causing the host-side QEMU process to crash, resulting in denial of service for that VM or workload. No source in the bundle indicates active exploitation, public exploit availability, or broader compromise.

Researcher notes

Evidence is strongest for the described QEMU e1000 loopback short-frame path and Red Hat product impact. The bundle does not provide a specific fixed version, patch commit, or exploit proof. Validate against vendor advisories before declaring remediation complete.

Mitigation direction

  • Check Red Hat advisories and errata for fixed qemu-kvm or rhcos builds.
  • Prioritize affected virtualization hosts running RHEL 9, RHEL 10, or OpenShift 4 rhcos.
  • Identify VMs configured with the QEMU e1000 virtual network device.
  • Apply vendor-provided updates or mitigations when available.
  • Consider reducing e1000 usage where operationally feasible and vendor-supported.

Validation and detection

  • Inventory qemu-kvm versions and platform releases on virtualization hosts.
  • Confirm whether hosts match affected Red Hat product entries.
  • Review VM definitions for e1000 virtual NIC usage.
  • Monitor host logs for unexpected QEMU process crashes.
  • Track Red Hat CVE and Bugzilla entries for remediation status.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-12464 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.53.6redhat

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2025-12464Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Made public.

  2. Source timelineredhat

    Reported to Red Hat.

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorqemuqemu, 8.1.0unaffected
Red HatRed Hat Enterprise Linux 10qemu-kvmaffected
Red HatRed Hat Enterprise Linux 6qemu-kvmunaffected
Red HatRed Hat Enterprise Linux 7qemu-kvmunaffected
Red HatRed Hat Enterprise Linux 7qemu-kvm-maunaffected
Red HatRed Hat Enterprise Linux 8virt:rhel/qemu-kvmunaffected
Red HatRed Hat Enterprise Linux 9qemu-kvmaffected
Red HatRed Hat OpenShift Container Platform 4rhcosaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.