# CVE-2022-36661: Null dereference in n/a

> Attackers can cause a Denial of Service in the xhyve hypervisor via a NULL pointer dereference in the vi_pci_read component.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2022
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-f499-35rg-394j

## What is CVE-2022-36661?

CVE-2022-36661 is a medium-severity vulnerability in n/a, published on 7 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

xhyve commit dfbe09b was discovered to contain a NULL pointer dereference via the component vi_pci_read(). This vulnerability allows attackers to cause a Denial of Service via unspecified vectors.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Xhyve Project Xhyve.

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

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

## Is CVE-2022-36661 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36660](https://insights.sbomify.com/CVE-2022-36660/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-35867](https://insights.sbomify.com/CVE-2022-35867/): Memory corruption in xhyve (high 7.5)
- [CVE-2022-36659](https://insights.sbomify.com/CVE-2022-36659/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36661 is a medium-severity vulnerability in n/a, published on 7 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36661 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-36661/ (Markdown: https://insights.sbomify.com/CVE-2022-36661/index.md)
```

## Sources

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

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