LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50136: RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event

In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event If siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn't been received completely, and should not report IW_CM_EVENT_CONNECT_REPLY in this case. This may trigger a call trace in iw_cm. A simple way to trigger this: server: ib_send_lat client: ib_send_lat -R <server_ip> The call trace looks like this: kernel BUG at drivers/infiniband/core/iwcm.c:894! invalid opcode: 0000 [#1] PREEMPT SMP NOPTI <...> Workqueue: iw_cm_wq cm_work_handler [iw_cm] Call Trace: <TASK> cm_work_handler+0x1dd/0x370 [iw_cm] process_one_work+0x1e2/0x3b0 worker_thread+0x49/0x2e0 ? rescuer_thread+0x370/0x370 kthread+0xe5/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30 </TASK>

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50136 is a Linux kernel RDMA/siw bug that can trigger a kernel BUG and call trace during connection handling. The disclosed impact is system instability, not data theft. Organizations using Linux RDMA SoftiWARP should prioritize kernel updates through their vendor or stable kernel source.

Executive priority

Treat as a targeted infrastructure stability issue. It is not currently supported as actively exploited, but affected RDMA/siw systems could crash or become unstable. Patch during the next appropriate maintenance window, faster for production RDMA workloads.

Technical view

The flaw is in Linux RDMA/siw handling of MPA replies. When siw_recv_mpa_rr returns -EAGAIN, an incomplete reply could still report IW_CM_EVENT_CONNECT_REPLY, causing duplicated event handling and a BUG in drivers/infiniband/core/iwcm.c. Stable kernel commits address the incorrect event reporting.

Likely exposure

Exposure is most relevant to Linux systems using RDMA/siw. The CVE record lists affected Linux versions including 5.3, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, and 6.0. Systems without RDMA/siw use are less likely to be exposed.

Exploitation context

The source describes a simple reproducer using RDMA latency tooling between a server and client. No CISA KEV listing or cited source indicates active exploitation. The demonstrated outcome is a kernel BUG/call trace, suggesting denial-of-service or stability risk in exposed RDMA/siw environments.

Researcher notes

The record lacks CVSS, CWE, and detailed impact scoring. The affected-version data is kernel-centric and should be reconciled with distribution backports. Analysis should focus on RDMA/siw reachability, module use, and whether the referenced stable commits are present.

Mitigation direction

  • Update affected Linux kernels to a vendor or stable release containing the referenced fixes.
  • Prioritize systems where RDMA/siw is enabled or used in production.
  • If patch timing is constrained, check vendor guidance for safe temporary exposure reduction.
  • Monitor vendor advisories for backported fixes in distribution kernels.

Validation and detection

  • Inventory Linux kernel versions across RDMA-capable hosts.
  • Confirm whether RDMA/siw is enabled or used.
  • Compare installed kernels against vendor fixed builds or referenced stable commits.
  • Review kernel logs for iw_cm BUG or RDMA/siw connection-related call traces.
Prepared
Confidence
medium
Sources
8

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-2022-50136 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
7Source 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
LinuxLinux6c52fdc244b5ccc468006fd65a504d4ee33743c7, 6c52fdc244b5ccc468006fd65a504d4ee33743c7, 6c52fdc244b5ccc468006fd65a504d4ee33743c7, 6c52fdc244b5ccc468006fd65a504d4ee33743c7, 6c52fdc244b5ccc468006fd65a504d4ee33743c7, 6c52fdc244b5ccc468006fd65a504d4ee33743c7unaffected
LinuxLinux5.3, 0, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

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