| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-49606: RDMA/irdma: Fix sleep from invalid context BUG |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| RDMA/irdma: Fix sleep from invalid context BUG |
| |
| Taking the qos_mutex to process RoCEv2 QP's on netdev events causes a |
| kernel splat. |
| |
| Fix this by removing the handling for RoCEv2 in |
| irdma_cm_teardown_connections that uses the mutex. This handling is only |
| needed for iWARP to avoid having connections established while the link is |
| down or having connections remain functional after the IP address is |
| removed. |
| |
| BUG: sleeping function called from invalid context at kernel/locking/mutex. |
| Call Trace: |
| kernel: dump_stack+0x66/0x90 |
| kernel: ___might_sleep.cold.92+0x8d/0x9a |
| kernel: mutex_lock+0x1c/0x40 |
| kernel: irdma_cm_teardown_connections+0x28e/0x4d0 [irdma] |
| kernel: ? check_preempt_curr+0x7a/0x90 |
| kernel: ? select_idle_sibling+0x22/0x3c0 |
| kernel: ? select_task_rq_fair+0x94c/0xc90 |
| kernel: ? irdma_exec_cqp_cmd+0xc27/0x17c0 [irdma] |
| kernel: ? __wake_up_common+0x7a/0x190 |
| kernel: irdma_if_notify+0x3cc/0x450 [irdma] |
| kernel: ? sched_clock_cpu+0xc/0xb0 |
| kernel: irdma_inet6addr_event+0xc6/0x150 [irdma] |
| |
| The Linux kernel CVE team has assigned CVE-2022-49606 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.14 with commit 146b9756f14c04894226fb97e2f102f217139c27 and fixed in 5.15.58 with commit a4c5115140ed1833197bad9a6b80265840ff427f |
| Issue introduced in 5.14 with commit 146b9756f14c04894226fb97e2f102f217139c27 and fixed in 5.18.15 with commit 2cae7e519032e4b4672cb9204d5586a441924364 |
| Issue introduced in 5.14 with commit 146b9756f14c04894226fb97e2f102f217139c27 and fixed in 5.19 with commit cc0315564d6eec91c716d314b743321be24c70b3 |
| |
| 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-49606 |
| 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/hw/irdma/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/a4c5115140ed1833197bad9a6b80265840ff427f |
| https://git.kernel.org/stable/c/2cae7e519032e4b4672cb9204d5586a441924364 |
| https://git.kernel.org/stable/c/cc0315564d6eec91c716d314b743321be24c70b3 |
