drm/amd/display: avoid using null object of framebuffer
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: avoid using null object of framebuffer
Instead of using state->fb->obj[0] directly, get object from framebuffer by calling drm_gem_fb_get_obj() and return error code when object is null to avoid using null object of framebuffer.
(cherry picked from commit 73dd0ad9e5dad53766ea3e631303430116f834b3)
From the CVE record · Linux
The Linux kernel’s AMD display code could use a null framebuffer object. The fix returns an error instead; the input does not specify attacker capabilities or the conditions needed to trigger the issue.
Engineers running Linux kernels with AMD display support should check whether their kernel includes the fix; affected versions are not specified.