Skip to main content
Mallory
← Back to News
cloud-service-vulnerabilityproof-of-concept-release

QEMU QXL Heap Overflows Expose Hosts to Guest-to-Host Memory Corruption

Vulnerability Disclosure · 2 sources · Updated 5mo ago · First seen Apr 11, 2026

QEMU QXL Heap Overflows Expose Hosts to Guest-to-Host Memory Corruption

STAR Labs disclosed two vulnerabilities in QEMU’s QXL para-virtualized video device, tracked as CVE-2021-4206 and CVE-2021-4207, that can trigger heap overflows during cursor handling. In the first flaw, guest-controlled cursor width and height values can cause an integer overflow in cursor_alloc(), leading to an undersized heap allocation before qxl_unpack_chunks() copies more data than allocated with memcpy(). In the second, a race condition allows guest-controlled cursor metadata to change after allocation but before size calculations, creating a mismatch that again lets qxl_unpack_chunks() write past the heap buffer.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Dec 28, 2021 – Mar 28, 2022
  1. Mar 28, 20225y ago

    QEMU patches CVE-2021-4206 and CVE-2021-4207

    The vendor released fixes for CVE-2021-4206 and CVE-2021-4207, two QXL-related heap overflow vulnerabilities in QEMU. The flaws could be exploited by a highly privileged attacker inside a guest VM using a QXL video device with VNC graphics.

  2. Dec 28, 20215y ago

    STAR Labs reports QEMU QXL heap overflow flaws to vendor

    STAR Labs disclosed two QEMU QXL heap overflow vulnerabilities, CVE-2021-4206 and CVE-2021-4207, to the vendor. Both issues involved guest-controlled cursor metadata leading to heap corruption under specific QXL and VNC configurations.

Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.