Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50136

RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event

High7.5EPSS 0.62%
Published
Updated
Reserved
Assigned by
Linux

Description

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>

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50136, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.62% · top 50% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 11edf0bba15ea9df49478affec7974f351bb2f6e
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 9ade92ddaf2347fb34298c02080caaa3cdd7c27b
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < f6e26e1a5f600b760dc32135d3fac846eabe09e7
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 0066246d2d7e2619f3ecf3cf07333c59e6e7d84d
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 1434de50a5d9dab91c8ce031bc23b3e2178379c5
    • affected 6c52fdc244b5ccc468006fd65a504d4ee33743c7 – < 3056fc6c32e613b760422b94c7617ac9a24a4721
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.4.211 – ≤ 5.4.*
    • unaffected 5.10.137 – ≤ 5.10.*
    • unaffected 5.15.61 – ≤ 5.15.*
    • unaffected 5.18.18 – ≤ 5.18.*
    • unaffected 5.19.2 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50136 badge
[![CVE-2022-50136](https://trackcve.app/badge/CVE-2022-50136.svg)](https://trackcve.app/cve/CVE-2022-50136)

Record last updated .