| 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-49925: RDMA/core: Fix null-ptr-deref in ib_core_cleanup() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| RDMA/core: Fix null-ptr-deref in ib_core_cleanup() |
| |
| KASAN reported a null-ptr-deref error: |
| |
| KASAN: null-ptr-deref in range [0x0000000000000118-0x000000000000011f] |
| CPU: 1 PID: 379 |
| Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) |
| RIP: 0010:destroy_workqueue+0x2f/0x740 |
| RSP: 0018:ffff888016137df8 EFLAGS: 00000202 |
| ... |
| Call Trace: |
| ib_core_cleanup+0xa/0xa1 [ib_core] |
| __do_sys_delete_module.constprop.0+0x34f/0x5b0 |
| do_syscall_64+0x3a/0x90 |
| entry_SYSCALL_64_after_hwframe+0x63/0xcd |
| RIP: 0033:0x7fa1a0d221b7 |
| ... |
| |
| It is because the fail of roce_gid_mgmt_init() is ignored: |
| |
| ib_core_init() |
| roce_gid_mgmt_init() |
| gid_cache_wq = alloc_ordered_workqueue # fail |
| ... |
| ib_core_cleanup() |
| roce_gid_mgmt_cleanup() |
| destroy_workqueue(gid_cache_wq) |
| # destroy an unallocated wq |
| |
| Fix this by catching the fail of roce_gid_mgmt_init() in ib_core_init(). |
| |
| The Linux kernel CVE team has assigned CVE-2022-49925 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.3 with commit 03db3a2d81e6e84f3ed3cb9e087cae17d762642b and fixed in 5.4.224 with commit af8fb5a0600e9ae29950e9422a032c3c22649ee5 |
| Issue introduced in 4.3 with commit 03db3a2d81e6e84f3ed3cb9e087cae17d762642b and fixed in 5.10.154 with commit d360e875c011a005628525bf290322058927e7dc |
| Issue introduced in 4.3 with commit 03db3a2d81e6e84f3ed3cb9e087cae17d762642b and fixed in 5.15.78 with commit 6b3d5dcb12347f3518308c2c9d2cf72453a3e1e5 |
| Issue introduced in 4.3 with commit 03db3a2d81e6e84f3ed3cb9e087cae17d762642b and fixed in 6.0.8 with commit ab817f75e5e0fa58d9be0825da6a7b7d8a1fa1d9 |
| Issue introduced in 4.3 with commit 03db3a2d81e6e84f3ed3cb9e087cae17d762642b and fixed in 6.1 with commit 07c0d131cc0fe1f3981a42958fc52d573d303d89 |
| |
| 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-49925 |
| 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/core/device.c |
| drivers/infiniband/core/nldev.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/af8fb5a0600e9ae29950e9422a032c3c22649ee5 |
| https://git.kernel.org/stable/c/d360e875c011a005628525bf290322058927e7dc |
| https://git.kernel.org/stable/c/6b3d5dcb12347f3518308c2c9d2cf72453a3e1e5 |
| https://git.kernel.org/stable/c/ab817f75e5e0fa58d9be0825da6a7b7d8a1fa1d9 |
| https://git.kernel.org/stable/c/07c0d131cc0fe1f3981a42958fc52d573d303d89 |
