drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2631ac1ac328189031d1aefbbd4929050f72fb23 · < 4ae3e16f4b3bf64140f773629b765d605ee079a9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Avoid NULL dereference in dc_dmub_srv error paths
In dc_dmub_srv_log_diagnostic_data() and dc_dmub_srv_enable_dpia_trace().
Both functions check:
if (!dc_dmub_srv || !dc_dmub_srv->dmub)
and then call DC_LOG_ERROR() inside that block.
DC_LOG_ERROR() uses dc_dmub_srv->ctx internally. So if dc_dmub_srv is NULL, the logging itself can dereference a NULL pointer and cause a crash.
Fix this by splitting the checks.
From the CVE record · Linux
The Linux kernel’s AMD display DMUB service can dereference a NULL pointer while logging an error, causing a crash. The input does not specify how an attacker could trigger the error, whether access or authentication is required, or whether user interaction is needed.
Engineers running Linux kernels with AMD display support should check whether their kernel is affected; affected versions are not specified.