LiveActive security incident?Get immediate response
CVE Record

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

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()").

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel RDMA/mlx4 flaw caused by a user-controlled size value wrapping during a bit shift. The public record confirms a kernel fix but does not provide CVSS, impact, or exploitation evidence. Treat it as a targeted kernel maintenance item, especially for systems using RDMA/mlx4 functionality.

Executive priority

Do not treat this as internet-scale based on the provided evidence. Prioritize kernel update validation for RDMA-capable Linux hosts, and escalate only if your vendor assigns higher severity or reports exploitation.

Technical view

In RDMA/mlx4 set_user_sq_size(), ucmd->log_sq_bb_count is user controlled and can cause shift wrapping. The kernel fix uses check_shl_overflow(), mirroring a prior RDMA/hns hardening change. The source bundle lists multiple stable kernel commits and affected Linux version lines, but no CWE, CVSS, or detailed impact.

Likely exposure

Exposure is most plausible on Linux systems running affected kernels where RDMA/mlx4 code is present and reachable. The bundle does not prove exposure for systems without this driver or RDMA use.

Exploitation context

The source bundle does not cite active exploitation, public exploit availability, or KEV inclusion. It only states that a user-controlled field can trigger shift wrapping in kernel RDMA/mlx4 logic.

Researcher notes

Key unknowns are impact, reachable privilege boundary, and distro backport status. The strongest source detail is the root cause and fix pattern: a user-controlled shift now guarded by check_shl_overflow().

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes through your distribution or kernel supplier.
  • Check vendor advisories for package names, backports, and any operational mitigations.
  • Prioritize hosts with RDMA/mlx4 enabled or workloads that expose RDMA interfaces to users.
  • If RDMA/mlx4 is unnecessary, assess disabling or removing that exposure under vendor guidance.

Validation and detection

  • Inventory Linux kernel versions against the affected version list in the CVE record.
  • Identify hosts using RDMA/mlx4 functionality or related kernel modules.
  • Confirm the relevant stable fix is present in vendor kernel changelogs or source packages.
  • Document any systems deferred from patching and the reason for exception.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54168 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux839041329fd3410e07d614f81e75bb43367d8f89, 839041329fd3410e07d614f81e75bb43367d8f89, 839041329fd3410e07d614f81e75bb43367d8f89, 839041329fd3410e07d614f81e75bb43367d8f89, 839041329fd3410e07d614f81e75bb43367d8f89, 839041329fd3410e07d614f81e75bb43367d8f89, 839041329fd3410e07d614f81e75bb43367d8f89, 839041329fd3410e07d614f81e75bb43367d8f89unaffected
LinuxLinux2.6.24, 0, 4.19.283, 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.