# CVE-2022-26361: Memory corruption in xen

> Improper handling of IOMMU reserved memory regions in Xen can lead to memory corruption or denial of service via DMA from specific PCI devices.

- **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:** Yes
- **Published:** 5 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-26361, DEBIAN-CVE-2022-26361, GHSA-c3mw-fh2q-7xx4, UBUNTU-CVE-2022-26361

## What is CVE-2022-26361?

CVE-2022-26361 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 5 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IOMMU: RMRR (VT-d) and unity map (AMD-Vi) handling issues T[his CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] Certain PCI devices in a system might be assigned Reserved Memory Regions (specified via Reserved Memory Region Reporting, "RMRR") for Intel VT-d or Unity Mapping ranges for AMD-Vi. These are typically used for platform tasks such as legacy USB emulation. Since the precise purpose of these regions is unknown, once a device associated with such a region is active, the mappings of these regions need to remain continuouly accessible by the device. This requirement has been violated. Subsequent DMA or interrupts from the device may have unpredictable behaviour, ranging from IOMMU faults to memory corruption.

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

It affects 3 products.


Products: Debian Debian Linux, Fedoraproject Fedora, Xen Xen.

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

Apply the vendor's patch.

## Is CVE-2022-26361 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26361 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 5 Apr 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-26361 in the wild and no public exploit code.

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

## Sources

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

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