# CVE-2023-54028: RDMA/rxe: Fix the error "trying to register non-static key in rxe_cleanup_task"

> A null pointer dereference in the Linux kernel RDMA/rxe driver allows remote attackers to cause a denial of service via crafted packets.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54028, DEBIAN-CVE-2023-54028, GHSA-4jmf-j564-cpmx, ROOT-OS-DEBIAN-11-CVE-2023-54028, ROOT-OS-UBUNTU-2204-CVE-2023-54028, UBUNTU-CVE-2023-54028

## What is CVE-2023-54028?

CVE-2023-54028 is a vulnerability in Linux, published on 24 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 the error "trying to register non-static key in rxe_cleanup_task"

In the function rxe_create_qp(), rxe_qp_from_init() is called to
initialize qp, internally things like rxe_init_task are not setup until
rxe_qp_init_req().

If an error occurred before this point then the unwind will call
rxe_cleanup() and eventually to rxe_qp_do_cleanup()/rxe_cleanup_task()
which will oops when trying to access the uninitialized spinlock.

If rxe_init_task is not executed, rxe_cleanup_task will not be called.

## Which versions are affected by CVE-2023-54028?


## How do I fix CVE-2023-54028?

Apply the vendor's patch.

## Is CVE-2023-54028 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54028 and fix it if it is affected.

What it is: CVE-2023-54028 is a vulnerability in Linux, published on 24 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-2023-54028 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-2023-54028/ (Markdown: https://insights.sbomify.com/CVE-2023-54028/index.md)
```

## Sources

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

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