| From bippy-1.1.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-49931: IB/hfi1: Correctly move list in sc_disable() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| IB/hfi1: Correctly move list in sc_disable() |
| |
| Commit 13bac861952a ("IB/hfi1: Fix abba locking issue with sc_disable()") |
| incorrectly tries to move a list from one list head to another. The |
| result is a kernel crash. |
| |
| The crash is triggered when a link goes down and there are waiters for a |
| send to complete. The following signature is seen: |
| |
| BUG: kernel NULL pointer dereference, address: 0000000000000030 |
| [...] |
| Call Trace: |
| sc_disable+0x1ba/0x240 [hfi1] |
| pio_freeze+0x3d/0x60 [hfi1] |
| handle_freeze+0x27/0x1b0 [hfi1] |
| process_one_work+0x1b0/0x380 |
| ? process_one_work+0x380/0x380 |
| worker_thread+0x30/0x360 |
| ? process_one_work+0x380/0x380 |
| kthread+0xd7/0x100 |
| ? kthread_complete_and_exit+0x20/0x20 |
| ret_from_fork+0x1f/0x30 |
| |
| The fix is to use the correct call to move the list. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49931 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.4.157 with commit d997d4e4365f7e59cf6b59c70f966c56d704b64f and fixed in 5.4.224 with commit 25760a41e3802f54aadcc31385543665ab349b8e |
| Issue introduced in 5.10.77 with commit d98883f6c33e0d960afedcecaa92fc2b61fec383 and fixed in 5.10.154 with commit 7c4260f8f188df32414a5ecad63e8b934c2aa3f0 |
| Issue introduced in 5.15 with commit 13bac861952a78664907a0f927d3e874e9a59034 and fixed in 5.15.78 with commit ba95409d6b580501ff6d78efd00064f7df669926 |
| Issue introduced in 5.15 with commit 13bac861952a78664907a0f927d3e874e9a59034 and fixed in 6.0.8 with commit b8bcff99b07cc175a6ee12a52db51cdd2229586c |
| Issue introduced in 5.15 with commit 13bac861952a78664907a0f927d3e874e9a59034 and fixed in 6.1 with commit 1afac08b39d85437187bb2a92d89a741b1078f55 |
| Issue introduced in 5.14.16 with commit 5d33bd6b4d4d035e42733592899918a18f2540da |
| |
| 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-49931 |
| 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/hfi1/pio.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/25760a41e3802f54aadcc31385543665ab349b8e |
| https://git.kernel.org/stable/c/7c4260f8f188df32414a5ecad63e8b934c2aa3f0 |
| https://git.kernel.org/stable/c/ba95409d6b580501ff6d78efd00064f7df669926 |
| https://git.kernel.org/stable/c/b8bcff99b07cc175a6ee12a52db51cdd2229586c |
| https://git.kernel.org/stable/c/1afac08b39d85437187bb2a92d89a741b1078f55 |
