# CVE-2023-54168: RDMA/mlx4: Prevent shift wrapping in set_user_sq_size()

> A user-controlled shift operation in the Linux kernel RDMA driver can wrap, potentially causing undefined behavior or denial of service.

- **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:** 30 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-54168, DEBIAN-CVE-2023-54168, GHSA-54vr-v43g-gq47, UBUNTU-CVE-2023-54168

## What is CVE-2023-54168?

CVE-2023-54168 is a high-severity vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

RDMA/mlx4: Prevent shift wrapping in set_user_sq_size()

The ucmd->log_sq_bb_count variable is controlled by the user so this
shift can wrap.  Fix it by using check_shl_overflow() in the same way
that it was done in commit 515f60004ed9 ("RDMA/hns: Prevent undefined
behavior in hns_roce_set_user_sq_size()").

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


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

Apply the vendor's patch.

## Is CVE-2023-54168 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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