Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2021-4207: QEMU QXL Cursor Double-Fetch Heap Buffer Overflow

Published Apr 29, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.2High · v3.1
EPSS0.40%35th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
Debian ProjectQemuRed Hat
IdentifiersCVE-2021-4207CWE-367

CVE-2021-4207 is a time-of-check/time-of-use flaw in QEMU's QXL display-device emulation, in the QXL cursor-command handling path. The qxl_cursor function fetches guest-controlled cursor width and height values to allocate a cursor object, then fetches the fields again when calculating the amount of cursor data to copy. Because the cursor structure is in guest-controlled RAM, a guest can race these operations and enlarge the dimensions after allocation. The resulting allocation-and-copy size mismatch causes qxl_unpack_chunks to copy data beyond the heap buffer with memcpy.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A privileged attacker in an affected guest can trigger a heap-based buffer overflow in the host QEMU process. Successful exploitation can crash the QEMU process, causing denial of service for the virtual machine, and may permit arbitrary code execution in the security context of the QEMU process.

Mitigation

If you can’t patch tonight, do this now.

Do not run untrusted code or drivers inside guest operating systems. Where operationally feasible, avoid configuring affected guests with the QXL video device and VNC server graphics until patched.

Remediation

Patch, then assume compromise.

Apply the QEMU vendor fix released on 2022-03-28, or the corresponding security update supplied by the operating-system or virtualization-platform vendor. Rocky Linux 8 deployments should apply the applicable CIQ crlsa-2022_5821 package updates.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
QemuQemuapplication
Red HatRed Hat Enterprise Linuxoperating_system
FAQ

Frequently asked questions

Is CVE-2021-4207 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2021-4207 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2021-4207?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2021-4207.
Is there a patch for CVE-2021-4207?
Apply the QEMU vendor fix released on 2022-03-28, or the corresponding security update supplied by the operating-system or virtualization-platform vendor. Rocky Linux 8 deployments should apply the applicable CIQ crlsa-2022_5821 package updates.
What products are affected by CVE-2021-4207?
Qemu, Debian Project Debian Linux, and Red Hat Enterprise Linux.
How severe is CVE-2021-4207?
CVE-2021-4207 has a CVSS v3.1 score of 8.2 (High) and an EPSS score of 0.40% (35th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.