# CVE-2021-36922: Privilege escalation in n/a

> Local attackers can exploit a flaw in the Realtek USB driver to escalate privileges, execute code, cause denial of service, or disclose information.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h6h5-vhg7-36q2

## What is CVE-2021-36922?

CVE-2021-36922 is a high-severity vulnerability in n/a, published on 2 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RtsUpx.sys in Realtek RtsUpx USB Utility Driver for Camera/Hub/Audio through 1.14.0.0 allows local low-privileged users to achieve unauthorized access to USB devices (Escalation of Privileges, Denial of Service, Code Execution, and Information Disclosure) via a crafted Device IO Control packet to a device.

## Which versions are affected by CVE-2021-36922?

It affects 1 product.


Products: Realtek Rtsupx Usb Utility Driver.

## How do I fix CVE-2021-36922?

No fix has been published for CVE-2021-36922 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-36922 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-36923](https://insights.sbomify.com/CVE-2021-36923/): Privilege escalation in n/a (high 7.8)
- [CVE-2021-36924](https://insights.sbomify.com/CVE-2021-36924/): Race condition in n/a (high 7.8)
- [CVE-2021-36925](https://insights.sbomify.com/CVE-2021-36925/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36922 and fix it if it is affected.

What it is: CVE-2021-36922 is a high-severity vulnerability in n/a, published on 2 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-36922 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-2021-36922/ (Markdown: https://insights.sbomify.com/CVE-2021-36922/index.md)
```

## Sources

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

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