| From bippy-7c5fe7eed585 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-49133: drm/amdkfd: svm range restore work deadlock when process exit |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| drm/amdkfd: svm range restore work deadlock when process exit |
| |
| kfd_process_notifier_release flush svm_range_restore_work |
| which calls svm_range_list_lock_and_flush_work to flush deferred_list |
| work, but if deferred_list work mmput release the last user, it will |
| call exit_mmap -> notifier_release, it is deadlock with below backtrace. |
| |
| Move flush svm_range_restore_work to kfd_process_wq_release to avoid |
| deadlock. Then svm_range_restore_work take task->mm ref to avoid mm is |
| gone while validating and mapping ranges to GPU. |
| |
| Workqueue: events svm_range_deferred_list_work [amdgpu] |
| Call Trace: |
| wait_for_completion+0x94/0x100 |
| __flush_work+0x12a/0x1e0 |
| __cancel_work_timer+0x10e/0x190 |
| cancel_delayed_work_sync+0x13/0x20 |
| kfd_process_notifier_release+0x98/0x2a0 [amdgpu] |
| __mmu_notifier_release+0x74/0x1f0 |
| exit_mmap+0x170/0x200 |
| mmput+0x5d/0x130 |
| svm_range_deferred_list_work+0x104/0x230 [amdgpu] |
| process_one_work+0x220/0x3c0 |
| |
| The Linux kernel CVE team has assigned CVE-2022-49133 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.14 with commit 42de677f79999791bee4e21be318c32d90ab62c6 and fixed in 5.16.20 with commit a6be83086e91891081e0589e4b4645bf4643e897 |
| Issue introduced in 5.14 with commit 42de677f79999791bee4e21be318c32d90ab62c6 and fixed in 5.17.3 with commit 858822905f4bf44100d63c5e22e263109976f7cb |
| Issue introduced in 5.14 with commit 42de677f79999791bee4e21be318c32d90ab62c6 and fixed in 5.18 with commit 6225bb3a88d22594aacea2485dc28ca12d596721 |
| |
| 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-49133 |
| 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/gpu/drm/amd/amdkfd/kfd_process.c |
| drivers/gpu/drm/amd/amdkfd/kfd_svm.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/a6be83086e91891081e0589e4b4645bf4643e897 |
| https://git.kernel.org/stable/c/858822905f4bf44100d63c5e22e263109976f7cb |
| https://git.kernel.org/stable/c/6225bb3a88d22594aacea2485dc28ca12d596721 |
