CVE-2022-50127: RDMA/rxe: Fix error unwind in rxe_create_qp()
In the Linux kernel, the following vulnerability has been resolved:
RDMA/rxe: Fix error unwind in rxe_create_qp()
In the function rxe_create_qp(), rxe_qp_from_init() is called to
initialize qp, internally things like the spin locks are not setup until
rxe_qp_init_req().
If an error occures 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.
Move the spinlock initializations earlier before any failures.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50127 is a Linux kernel RDMA/rxe bug that can make the kernel crash during an error cleanup path. It is not listed as actively exploited, and no CVSS score is provided. Business urgency is highest for systems using or exposing RDMA rxe/Soft-RoCE functionality.
Executive priority
Treat as a targeted kernel availability issue, not a broad emergency based on current evidence. Patch through normal kernel maintenance, with faster handling for RDMA-enabled infrastructure, HPC, storage, or low-latency environments that rely on rxe.
Technical view
In rxe_create_qp(), cleanup can run before required spin locks are initialized. The cleanup path reaches rxe_qp_do_cleanup()/rxe_cleanup_task() and can oops when accessing an uninitialized spinlock. The upstream fix moves spinlock initialization earlier, before possible failures.
Likely exposure
Most relevant exposure is Linux systems running affected kernels with RDMA rxe functionality present or enabled. The CVE record lists Linux as affected and references stable kernel fixes. Distribution kernels may have backported patches, so version alone may not prove exposure.
Exploitation context
The provided sources do not report active exploitation, public weaponization, or KEV listing. Exploitation context appears tied to triggering a specific RDMA/rxe queue-pair creation failure path. Impact described by sources is a kernel oops, implying availability risk.
Researcher notes
Evidence is limited to the CVE record and upstream stable commits. No CWE, CVSS, or exploitation evidence is provided. Validate exact affected ranges through upstream commits and distribution advisories because downstream kernels often carry backported fixes.
Mitigation direction
Update to a vendor kernel containing the referenced stable RDMA/rxe fix.
Prioritize hosts where RDMA rxe or Soft-RoCE is enabled or required.
If patch status is unclear, check Linux distribution security advisories.
Reduce unnecessary RDMA/rxe exposure where it is not operationally needed.
Validation and detection
Inventory Linux kernel versions and vendor backport status.
Identify systems with RDMA rxe or Soft-RoCE functionality enabled.
Compare deployed kernels against the referenced stable fix commits.
Review kernel logs for RDMA/rxe-related oops events.
Confirm remediation through vendor package metadata or kernel changelogs.
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-2022-50127 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.