# CVE-2022-29021: Memory corruption in n/a

> Attackers can cause denial of service or escalate privileges via a buffer overflow in the OpenRazer kernel driver.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2022
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2022-29021, GHSA-xm8g-mhgj-5vhv, UBUNTU-CVE-2022-29021

## What is CVE-2022-29021?

CVE-2022-29021 is a critical memory corruption vulnerability in n/a, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow vulnerability exists in the razerkbd driver of OpenRazer up to version v3.3.0 allows attackers to cause a Denial of Service (DoS) and possibly escalate their privileges via a crafted buffer sent to the matrix_custom_frame device.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-29021?

It affects 1 product.


Products: Openrazer Project Openrazer.

## How do I fix CVE-2022-29021?

Upgrade to a fixed version.

## Is CVE-2022-29021 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29022](https://insights.sbomify.com/CVE-2022-29022/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-29023](https://insights.sbomify.com/CVE-2022-29023/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-23467](https://insights.sbomify.com/CVE-2022-23467/): Out of Bounds Read in OpenRazer Driver (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29021 and fix it if it is affected.

What it is: CVE-2022-29021 is a critical memory corruption vulnerability in n/a, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29021 in the wild and no public exploit code.

Affected product: n/a. 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-2022-29021/ (Markdown: https://insights.sbomify.com/CVE-2022-29021/index.md)
```

## Sources

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

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