LiveActive security incident?Get immediate response
CVE Record

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

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.

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/rxe cleanup bug. Under an early error while creating a queue pair, the kernel could try to clean up an uninitialized task lock and oops. Business impact appears most likely availability risk, but the sources do not provide CVSS, attack requirements, or confirmed exploitation.

Executive priority

Treat as a targeted Linux kernel maintenance issue, not an emergency from current evidence. Escalate priority for systems that rely on RDMA/rxe or where kernel crashes would materially affect service availability.

Technical view

In rxe_create_qp(), rxe_qp_from_init() initializes the queue pair before rxe_qp_init_req() sets up rxe_init_task. If creation fails before that setup, unwind reaches rxe_cleanup_task() through rxe_cleanup() and can access an uninitialized spinlock. The fix avoids calling rxe_cleanup_task when rxe_init_task was not executed.

Likely exposure

Exposure is limited to Linux systems with affected kernel versions and the RDMA/rxe driver path in use. The bundle lists Linux as affected but provides incomplete version semantics and no distribution-specific advisory mapping.

Exploitation context

The bundle does not report active exploitation, KEV listing, public exploit code, or attacker prerequisites. It describes a kernel oops during an error path, so any exploitability beyond denial of service is not established by the provided sources.

Researcher notes

The key condition is cleanup after partial rxe_create_qp() initialization. Research should focus on whether reachable error paths can be triggered in deployed configurations and whether the impact remains an oops. Do not assume privilege level or remote reachability from this bundle alone.

Mitigation direction

  • Check Linux distribution advisories for CVE-2023-54028 and available kernel updates.
  • Prioritize systems using RDMA/rxe or Soft-RoCE functionality.
  • Apply vendor-supported kernel updates containing the referenced stable commits.
  • If RDMA/rxe is unnecessary, consider disabling it per vendor guidance.
  • Track compensating controls until distribution-specific fixes are confirmed.

Validation and detection

  • Inventory kernel versions across Linux hosts.
  • Identify hosts where RDMA/rxe functionality is enabled or loaded.
  • Map installed kernels to distribution advisories for CVE-2023-54028.
  • Confirm updated kernels include one of the referenced stable fixes.
  • Review crash logs for RDMA/rxe-related kernel oops messages.
Prepared
Confidence
medium
Sources
6

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-54028 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
5Source 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
LinuxLinux8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76, 8700e3e7c4857d28ebaa824509934556da0b3e76unaffected
LinuxLinux4.8, 0, 6.1.32, 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.