drm/amd/display: Fix potential memory leak in DMUB hw_init
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
5.10.455.12.125.13In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Fix potential memory leak in DMUB hw_init
[Why] On resume we perform DMUB hw_init which allocates memory: dm_resume->dm_dmub_hw_init->dc_dmub_srv_create->kzalloc That results in memory leak in suspend/resume scenarios.
[How] Allocate memory for the DC wrapper to DMUB only if it was not allocated before. No need to reallocate it on suspend/resume.
From the CVE record · Linux
The Linux kernel’s AMD display driver can leak memory when DMUB hardware initialization runs again after resume. The leak occurs during suspend/resume; the input does not specify an attacker action, access requirement, or other user interaction.
Engineers running Linux kernels with the AMD display driver should check their installations; affected versions are not specified.