[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025061816-CVE-2022-50136-f85e@gregkh>
Date: Wed, 18 Jun 2025 13:03:21 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50136: RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY event
From: Greg Kroah-Hartman <gregkh@...nel.org>
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>
The Linux kernel CVE team has assigned CVE-2022-50136 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.3 with commit 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and fixed in 5.4.211 with commit 11edf0bba15ea9df49478affec7974f351bb2f6e
Issue introduced in 5.3 with commit 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and fixed in 5.10.137 with commit 9ade92ddaf2347fb34298c02080caaa3cdd7c27b
Issue introduced in 5.3 with commit 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and fixed in 5.15.61 with commit f6e26e1a5f600b760dc32135d3fac846eabe09e7
Issue introduced in 5.3 with commit 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and fixed in 5.18.18 with commit 0066246d2d7e2619f3ecf3cf07333c59e6e7d84d
Issue introduced in 5.3 with commit 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and fixed in 5.19.2 with commit 1434de50a5d9dab91c8ce031bc23b3e2178379c5
Issue introduced in 5.3 with commit 6c52fdc244b5ccc468006fd65a504d4ee33743c7 and fixed in 6.0 with commit 3056fc6c32e613b760422b94c7617ac9a24a4721
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-50136
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/infiniband/sw/siw/siw_cm.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/11edf0bba15ea9df49478affec7974f351bb2f6e
https://git.kernel.org/stable/c/9ade92ddaf2347fb34298c02080caaa3cdd7c27b
https://git.kernel.org/stable/c/f6e26e1a5f600b760dc32135d3fac846eabe09e7
https://git.kernel.org/stable/c/0066246d2d7e2619f3ecf3cf07333c59e6e7d84d
https://git.kernel.org/stable/c/1434de50a5d9dab91c8ce031bc23b3e2178379c5
https://git.kernel.org/stable/c/3056fc6c32e613b760422b94c7617ac9a24a4721
Powered by blists - more mailing lists