[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091853-CVE-2022-50393-d5da@gregkh>
Date: Thu, 18 Sep 2025 15:34:07 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50393: drm/amdgpu: SDMA update use unlocked iterator
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: SDMA update use unlocked iterator
SDMA update page table may be called from unlocked context, this
generate below warning. Use unlocked iterator to handle this case.
WARNING: CPU: 0 PID: 1475 at
drivers/dma-buf/dma-resv.c:483 dma_resv_iter_next
Call Trace:
dma_resv_iter_first+0x43/0xa0
amdgpu_vm_sdma_update+0x69/0x2d0 [amdgpu]
amdgpu_vm_ptes_update+0x29c/0x870 [amdgpu]
amdgpu_vm_update_range+0x2f6/0x6c0 [amdgpu]
svm_range_unmap_from_gpus+0x115/0x300 [amdgpu]
svm_range_cpu_invalidate_pagetables+0x510/0x5e0 [amdgpu]
__mmu_notifier_invalidate_range_start+0x1d3/0x230
unmap_vmas+0x140/0x150
unmap_region+0xa8/0x110
The Linux kernel CVE team has assigned CVE-2022-50393 to this issue.
Affected and fixed versions
===========================
Fixed in 5.19.17 with commit b892c57a3a04c8de247ab9ee08a0a8cf53290e19
Fixed in 6.0.3 with commit 4ff3d517cebe8a29b9f3c302b5292bb1ce291e00
Fixed in 6.1 with commit 3913f0179ba366f7d7d160c506ce00de1602bbc4
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-50393
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/amdgpu/amdgpu_vm_sdma.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/b892c57a3a04c8de247ab9ee08a0a8cf53290e19
https://git.kernel.org/stable/c/4ff3d517cebe8a29b9f3c302b5292bb1ce291e00
https://git.kernel.org/stable/c/3913f0179ba366f7d7d160c506ce00de1602bbc4
Powered by blists - more mailing lists