# CVE-2022-21819: Misconfiguration in Jetson Nano, Jetson Nano 2GB

> An IOMMU misconfiguration in NVIDIA Jetson Linux allows physical attackers to access system memory via PCI, enabling code execution and privilege escalation.

- **Severity:** High 7.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5q8q-7qqw-cmj3

## What is CVE-2022-21819?

CVE-2022-21819 is a high-severity vulnerability in NVIDIA Jetson Nano, Jetson Nano 2GB, published on 11 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NVIDIA distributions of Jetson Linux contain a vulnerability where an error in the IOMMU configuration may allow an unprivileged attacker with physical access to the board direct read/write access to the entire system address space through the PCI bus. Such an attack could result in denial of service, code execution, escalation of privileges, and impact to data integrity and confidentiality. The scope impact may extend to other components.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Nvidia Jetson Linux.

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

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

## Is CVE-2022-21819 being exploited?

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

## Other vulnerabilities in NVIDIA Jetson Nano, Jetson Nano 2GB

- [CVE-2024-0108](https://insights.sbomify.com/CVE-2024-0108/): Memory corruption in NVIDIA Jetson AGX Xavier series, Jetson Xavier NX, Jetson TX2 series, Jetson TX2 NX, Jetson TX1, Jetson Nano series (high 8.7)
- [CVE-2026-24148](https://insights.sbomify.com/CVE-2026-24148/): Misconfiguration in Jetson Xavier Series and Jetson Orin Series (high 8.3)
- [CVE-2021-34372](https://insights.sbomify.com/CVE-2021-34372/): Integer overflow in NVIDIA Jetson TX2 series, TX2 NX, AGX Xavier series, Xavier NX (high 8.2)
- [CVE-2022-42269](https://insights.sbomify.com/CVE-2022-42269/): Information disclosure in Jetson AGX Xavier series, Jetson Xavier NX, Jetson TX1, Jetson TX2 series, Jetson TX2 NX (high 7.9)
- [CVE-2021-34373](https://insights.sbomify.com/CVE-2021-34373/): Memory corruption in NVIDIA Jetson TX1 (high 7.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21819 is a high-severity vulnerability in NVIDIA Jetson Nano, Jetson Nano 2GB, published on 11 Mar 2022. 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-2022-21819 in the wild and no public exploit code.

Affected product: NVIDIA Jetson Nano, Jetson Nano 2GB. 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-21819/ (Markdown: https://insights.sbomify.com/CVE-2022-21819/index.md)
```

## Sources

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

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