In the Linux kernel, the following vulnerability has been resolved:RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY eventIf siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn tbeen received completely, and should not report IW_CM_EVENT_CONNECT_REPLYin this case. This may trigger a call trace in iw_cm. A simple way totrigger 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>
In the Linux kernel, the following vulnerability has been resolved:RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY eventIf siw_recv_mpa_rr returns -EAGAIN, it means that the MPA reply hasn tbeen received completely, and should not report IW_CM_EVENT_CONNECT_REPLYin this case. This may trigger a call trace in iw_cm. A simple way totrigger 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>
In the Linux kernel, the followingvulnerability has been resolved:RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY eventIf siw_recv_mpa_rr returns -EAGAIN, it meansthat the MPA reply hasn tbeenreceived completely, and should notreport IW_CM_EVENT_CONNECT_REPLYin this case. This may trigger acall trace in iw_cm. A simple way totrigger 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>
A vulnerability was found in LinuxKernel up to 5.4.210/5.10.136/5.15.60/5.18.17/5.19.1 (Operating System) and classified as problematic.Impacted is confidentiality, integrity,and availability.Upgrading toversion 5.4.211, 5.10.137, 5.15.61,5.18.18 or 5.19.2 eliminates this vulnerability. Applying the patch 11edf0bba15ea9df49478affec7974f351bb2f6e/9ade92ddaf2347fb34298c02080caaa3cdd7c27b/f6e26e1a5f600b760dc32135d3fac846eabe09e7/0066246d2d7e2619f3ecf3cf07333c59e6e7d84d/1434de50a5d9dab91c8ce031bc23b3e2178379c5/3056fc6c32e613b760422b94c7617ac9a24a4721 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation issuggested to be upgradingto the latest version.
A vulnerability was found in LinuxKernel up to 5.4.210/5.10.136/5.15.60/5.18.17/5.19.1 (Operating System) and classified as problematic.Impacted is confidentiality, integrity,and availability.Upgrading toversion 5.4.211, 5.10.137, 5.15.61,5.18.18 or 5.19.2 eliminates this vulnerability. Applying the patch 11edf0bba15ea9df49478affec7974f351bb2f6e/9ade92ddaf2347fb34298c02080caaa3cdd7c27b/f6e26e1a5f600b760dc32135d3fac846eabe09e7/0066246d2d7e2619f3ecf3cf07333c59e6e7d84d/1434de50a5d9dab91c8ce031bc23b3e2178379c5/3056fc6c32e613b760422b94c7617ac9a24a4721 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation issuggested to be upgradingto the latest version.
In the Linux kernel, the followingvulnerability has been resolved:RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY eventIf siw_recv_mpa_rr returns -EAGAIN, it meansthat the MPA reply hasn tbeenreceived completely, and should notreport IW_CM_EVENT_CONNECT_REPLYin this case. This may trigger acall trace in iw_cm. A simple way totrigger 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>
In the Linux kernel, the followingvulnerability has been resolved:RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY eventIf siw_recv_mpa_rr returns -EAGAIN, it meansthat the MPA reply hasn tbeenreceived completely, and should notreport IW_CM_EVENT_CONNECT_REPLYin this case. This may trigger acall trace in iw_cm. A simple way totrigger 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>
A vulnerability was found in LinuxKernel up to 5.4.210/5.10.136/5.15.60/5.18.17/5.19.1 (Operating System) and classified as problematic.Impacted is confidentiality, integrity,and availability.Upgrading toversion 5.4.211, 5.10.137, 5.15.61,5.18.18 or 5.19.2 eliminates this vulnerability. Applying the patch 11edf0bba15ea9df49478affec7974f351bb2f6e/9ade92ddaf2347fb34298c02080caaa3cdd7c27b/f6e26e1a5f600b760dc32135d3fac846eabe09e7/0066246d2d7e2619f3ecf3cf07333c59e6e7d84d/1434de50a5d9dab91c8ce031bc23b3e2178379c5/3056fc6c32e613b760422b94c7617ac9a24a4721 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation issuggested to be upgradingto the latest version.
A vulnerability was found in LinuxKernel up to 5.4.210/5.10.136/5.15.60/5.18.17/5.19.1 (Operating System) and classified as problematic.Impacted is confidentiality, integrity,and availability.Upgrading toversion 5.4.211, 5.10.137, 5.15.61,5.18.18 or 5.19.2 eliminates this vulnerability. Applying the patch 11edf0bba15ea9df49478affec7974f351bb2f6e/9ade92ddaf2347fb34298c02080caaa3cdd7c27b/f6e26e1a5f600b760dc32135d3fac846eabe09e7/0066246d2d7e2619f3ecf3cf07333c59e6e7d84d/1434de50a5d9dab91c8ce031bc23b3e2178379c5/3056fc6c32e613b760422b94c7617ac9a24a4721 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation issuggested to be upgradingto the latest version.
In the Linux kernel, the followingvulnerability has been resolved:RDMA/siw: Fix duplicated reported IW_CM_EVENT_CONNECT_REPLY eventIf siw_recv_mpa_rr returns -EAGAIN, it meansthat the MPA reply hasn tbeenreceived completely, and should notreport IW_CM_EVENT_CONNECT_REPLYin this case. This may trigger acall trace in iw_cm. A simple way totrigger 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>