CVE-2022-1050· NVD / CVE Program· CNA redhat

A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device.

Noroxi assessment

Priority: Monitor (action score 35/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: qemu (Debian:10) 1:3.1+dfsg-8+deb10u10; qemu (Debian:12) 1:7.1+dfsg-2; qemu (openSUSE:Leap 15.4) 4.2.1-150200.79.1.

Low priority for now. Upgrade to qemu (Debian:10) 1:3.1+dfsg-8+deb10u10; qemu (Debian:12) 1:7.1+dfsg-2; qemu (openSUSE:Leap 15.4) 4.2.1-150200.79.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device. This flaw allows a crafted guest driver to execute HW commands when shared buffers are not yet allocated, potentially leading to a use-after-free condition.

HighCVSS 8.8 · v3.1—No exploit Fix available

Memory safety

Published: Mar 29, 2022
Updated: Jun 17, 2026
EPSS: 0.3% · 30th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
qemu	qemu	cpe:2.3:a:qemu:qemu

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

qemu qemubefore 2.20.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

n/a QEMU
- qemu 2.20.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:10	qemu	before 1:3.1+dfsg-8+deb10u10	1:3.1+dfsg-8+deb10u10
Debian:12	qemu	before 1:7.1+dfsg-2	1:7.1+dfsg-2
openSUSE:Leap 15.4	qemu	before 4.2.1-150200.79.1	4.2.1-150200.79.1
openSUSE:Leap 15.4	qemu-linux-user	before 6.2.0-150400.37.11.1	6.2.0-150400.37.11.1
openSUSE:Leap 15.4	qemu-testsuite	before 6.2.0-150400.37.11.2	6.2.0-150400.37.11.2
openSUSE:Leap Micro 5.3	qemu	before 6.2.0-150400.37.11.1	6.2.0-150400.37.11.1
openSUSE:Tumbleweed	qemu	before 7.1.0-12.1	7.1.0-12.1
SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS	qemu	before 3.1.1.1-150100.80.51.5	3.1.1.1-150100.80.51.5
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS	qemu	before 4.2.1-150200.79.1	4.2.1-150200.79.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-ESPOS	qemu	before 5.2.0-150300.121.2	5.2.0-150300.121.2
SUSE:Linux Enterprise Micro 5.3	qemu	before 6.2.0-150400.37.11.1	6.2.0-150400.37.11.1
SUSE:Linux Enterprise Server 12 SP5	qemu	before 3.1.1.1-66.1	3.1.1.1-66.1

Same product

qemu: all records

Other highest-scoring records for the same primary product.

CVE-2019-12928The QMP migrate command in QEMU version 4.0.0 and earlier is vulnerable to OS command injection, which allows the remote attacker to achieve
60This week
CVE-2015-8556Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
44Plan
CVE-2017-15118A stack-based buffer overflow vulnerability was found in NBD server implementation in qemu before 2.11 allowing a client to request an expor
43Plan

Published before and after this one in the same product

← EarlierCVE-2021-3748Mar 23, 2022 · A use-after-free vulnerability was found in the virtio-net device of QEMU.
30Monitor
← EarlierCVE-2021-3582Mar 25, 2022 · A flaw was found in the QEMU implementation of VMWare's paravirtual RDMA device.
26Monitor
Later →CVE-2021-20295Apr 1, 2022 · It was discovered that the update for the virt:rhel module in the RHSA-2020:4676 (https://access.redhat.com/errata/RHSA-2020:4676) erratum r
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:qemu	1:7.1+dfsg-2 · Debian:12	Package registry (OSV)
opensuse:qemu	6.2.0-150400.37.11.1 · openSUSE:Leap Micro 5.3	Package registry (OSV)
opensuse:qemu-linux-user	6.2.0-150400.37.11.1 · openSUSE:Leap 15.4	Package registry (OSV)
opensuse:qemu-testsuite	6.2.0-150400.37.11.2 · openSUSE:Leap 15.4	Package registry (OSV)
suse:qemu	6.2.0-150400.37.11.1 · SUSE:Linux Enterprise Micro 5.3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Changed
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

bugzilla.redhat.com/show_bug.cgi?id=2069625

Show all references (1 more)

lists.debian.org/debian-lts-announce/2023/03/msg00013.html

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records