# CVE-2022-50671: RDMA/rxe: Fix "kernel NULL pointer dereference" error

> A null pointer dereference in the Linux kernel RDMA subsystem allows attackers to cause a denial of service via crafted queue pair creation requests.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2022-50671, GHSA-9v66-cvmj-6924, UBUNTU-CVE-2022-50671

## What is CVE-2022-50671?

CVE-2022-50671 is a high-severity vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

RDMA/rxe: Fix "kernel NULL pointer dereference" error

When rxe_queue_init in the function rxe_qp_init_req fails,
both qp->req.task.func and qp->req.task.arg are not initialized.

Because of creation of qp fails, the function rxe_create_qp will
call rxe_qp_do_cleanup to handle allocated resource.

Before calling __rxe_do_task, both qp->req.task.func and
qp->req.task.arg should be checked.

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


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

Apply the vendor's patch.

## Is CVE-2022-50671 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50671 is a high-severity vulnerability in Linux, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50671 in the wild and no public exploit code.

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

## Sources

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

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