Linux kernel invalid work scheduling in AMD GPU thermal handling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1919696eedc1ed5c3ace229576e4fa322fb256dd · < 52c4c623474df0e19efa158057966f2a149bda28| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/pm/si: Don't schedule thermal work when queue isn't initialized
When DPM is turned off with the amdgpu.dpm=0 module parameter, the thermal work queue isn't initialized so we shouldn't schedule any work on it.
(cherry picked from commit bd018d36171a695952c6d391471c279c9e05c8b2)
From the CVE record · Linux
When DPM is disabled with the amdgpu.dpm=0 module parameter, the Linux kernel can schedule thermal work on a queue that was not initialized. The input does not describe an attacker action, authentication requirements, or user interaction.
Engineers running Linux kernels with AMD GPU power management should check whether they use amdgpu.dpm=0; affected versions are not specified.