This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Metrics
Affected Vendors & Products
References
History
Thu, 19 Jun 2025 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Title | drm/amdgpu: Init zone device and drm client after mode-1 reset on reload | kernel: drm/amdgpu: Init zone device and drm client after mode-1 reset on reload |
Metrics |
ssvc
|
Thu, 19 Jun 2025 14:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Thu, 19 Jun 2025 13:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Init zone device and drm client after mode-1 reset on reload In passthrough environment, when amdgpu is reloaded after unload, mode-1 is triggered after initializing the necessary IPs, That init does not include KFD, and KFD init waits until the reset is completed. KFD init is called in the reset handler, but in this case, the zone device and drm client is not initialized, causing app to create kernel panic. v2: Removing the init KFD condition from amdgpu_amdkfd_drm_client_create. As the previous version has the potential of creating DRM client twice. v3: v2 patch results in SDMA engine hung as DRM open causes VM clear to SDMA before SDMA init. Adding the condition to in drm client creation, on top of v1, to guard against drm client creation call multiple times. | This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
Sun, 04 May 2025 10:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Wed, 13 Nov 2024 02:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Redhat
Redhat enterprise Linux |
|
CPEs | cpe:/a:redhat:enterprise_linux:9 cpe:/o:redhat:enterprise_linux:9 |
|
Vendors & Products |
Redhat
Redhat enterprise Linux |

Status: REJECTED
Assigner: Linux
Published: 2024-05-30T15:03:59.678Z
Updated: 2025-06-19T13:03:48.081Z
Reserved: 2024-05-17T13:50:33.157Z
Link: CVE-2024-36022

Updated:

Status : Rejected
Published: 2024-05-30T15:15:49.263
Modified: 2025-06-19T14:15:45.160
Link: CVE-2024-36022
