drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
17a98c942cb106ec08564e8f43b5470a4dd5d3f6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG
There were multiple issues in that code.
First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock.
Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock.
Then we used down_read_trylock() instead of waiting for the reset to finish.
(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)
From the CVE record · Linux
The Linux kernel’s AMDGPU_INFO_READ_MMR_REG code has locking and memory-allocation errors that can cause a deadlock. This affects local use of the AMDGPU interface; the input does not specify authentication requirements.
Engineers running Linux kernels with the affected drm/amdgpu code should check their systems; affected versions are not specified.