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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 20.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux | < 6.8.0-38.38 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < any | UNKNOWN |
ubuntu | 24.04 | noarch | linux-aws | < 6.8.0-1011.12 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws-5.15 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-azure | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-azure | < any | UNKNOWN |
git.kernel.org/linus/f679fd6057fbf5ab34aaee28d58b7f81af0cbf48 (6.9-rc1)
git.kernel.org/stable/c/4f8154f775197d0021b690c2945d6a4d8094c8f6
git.kernel.org/stable/c/f679fd6057fbf5ab34aaee28d58b7f81af0cbf48
launchpad.net/bugs/cve/CVE-2024-36022
nvd.nist.gov/vuln/detail/CVE-2024-36022
security-tracker.debian.org/tracker/CVE-2024-36022
ubuntu.com/security/notices/USN-6893-1
ubuntu.com/security/notices/USN-6893-2
ubuntu.com/security/notices/USN-6893-3
ubuntu.com/security/notices/USN-6918-1
www.cve.org/CVERecord?id=CVE-2024-36022