drm/amd/display: Initialize get_bytes_per_element's default to 1
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c · < bc00d211da4ffad5314a2043b50bdc8ff8a33724| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/amd/display: Initialize get_bytes_per_element's default to 1
Variables, used as denominators and maybe not assigned to other values, should not be 0. bytes_per_element_y & bytes_per_element_c are initialized by get_bytes_per_element() which should never return 0.
This fixes 10 DIVIDE_BY_ZERO issues reported by Coverity.
From the CVE record · Linux
The Linux kernel’s AMD display code can use a zero value as a denominator because get_bytes_per_element() may return zero. The fix addresses ten divide-by-zero issues reported by Coverity. The input does not establish an attacker path or specify access, authentication, or user-interaction requirements.
Engineers running the Linux kernel with AMD display code should check their deployments; affected versions were not provided.