drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Correct the defined value for AMDGPU_DMUB_NOTIFICATION_MAX
[Why & How] It actually exposes '6' types in enum dmub_notification_type. Not 5. Using smaller number to create array dmub_callback & dmub_thread_offload has potential to access item out of array bound. Fix it.
From the CVE record · Linux
The Linux kernel’s AMD display code allocates notification callback arrays for five types even though six are defined, creating a potential out-of-bounds access. The input does not specify how an attacker could trigger it or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with AMD display code should check their versions; affected versions are not specified.