CVE-2026-89819
CVE CVE-2026-89819EUVD EUVD-2026-80419Published 2026-09-16T10:30:51.000ZLast changed 2026-09-16T14:39:00.000ZCVSS 7.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: validate plane degamma LUT size for private color prop Unlike the CRTC degamma path, which is guarded by amdgpu_dm_verify_lut_sizes(), the per-plane degamma LUT size was never validated before use. __set_dm_plane_degamma() passed the user-supplied size straight into __is_lut_linear() and, for a non-linear LUT, into __set_input_tf() -> __drm_lut_to_dc_gamma(), the latter always iterating MAX_COLOR_LUT_ENTRIES entries regardless of the actual LUT size. A malformed AMD_PLANE_DEGAMMA_LUT blob (e.g. a single entry) could thus trigger a divide-by-zero in __is_lut_linear() or an out-of-bounds read in __drm_lut_to_dc_gamma(). Reject any plane degamma LUT whose size does not match MAX_COLOR_LUT_ENTRIES, mirroring the invariant the code already asserts a few lines below (and which the CRTC path enforces). The AMD_PLANE_DEGAMMA_LUT property is only exposed on builds with AMD_PRIVATE_COLOR defined.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 0; 980f8710075acaeb226a94cde6dda8ffad30123c <e4c3ab59021e7c146a84b6671f0d530972bd58b4; 980f8710075acaeb226a94cde6dda8ffad30123c <f6f04d8ae5725bcc893bdc62e3467efd97255c5b; patch: 7.3-rc1; patch: 7.2.5; patch: 6.18.51; 980f8710075acaeb226a94cde6dda8ffad30123c <0b2615b8b54f58bbdf986dffb38cbc35214a5cc5; patch: 6.12.110; 980f8710075acaeb226a94cde6dda8ffad30123c <b10cc09b329245c6d95f8fa3e7f068575e3e0e9f; 6.8
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.