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

> Attackers can cause a denial of service via a null pointer dereference in the hwloc topology library's Linux CPU set handling.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2023
- **Updated:** 3 Oct 2024
- **Also known as:** AZL-28092, AZL-28595, AZL-34800, AZL-35071, CLSA-2026-1785768115, CLSA-2026-1785770281, DEBIAN-CVE-2022-47022, GHSA-wrgx-2383-98cr, JLSEC-2025-176, OESA-2023-1589, OESA-2023-1590, UBUNTU-CVE-2022-47022, openSUSE-SU-2024:13347-1

## What is CVE-2022-47022?

CVE-2022-47022 is a medium-severity vulnerability in n/a, published on 22 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in open-mpi hwloc 2.1.0 allows attackers to cause a denial of service or other unspecified impacts via glibc-cpuset in topology-linux.c.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Open-Mpi Hwloc.

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

Upgrade to a fixed version.

## Is CVE-2022-47022 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47022 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47022 is a medium-severity vulnerability in n/a, published on 22 Aug 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47022 exists.

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-47022/ (Markdown: https://insights.sbomify.com/CVE-2022-47022/index.md)
```

## Sources

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

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