CVE-2024-49892

drm/amd/display: Initialize get_bytes_per_element's default to 1

MEDIUM

5.5

CVSS Score

Published: October 21, 2024 at 06:01 PM UTC

Updated: October 15, 2026 at 01:19 AM UTC

2 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFP

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

All versionsv < 5.10.2275.11 ≤ v < 5.15.1685.16 ≤ v < 6.1.1136.11 ≤ v < 6.11.36.2 ≤ v < 6.6.556.7 ≤ v < 6.10.144.154562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c

Vendor states this is fixed in 1f9f8186e239222f1c8d3dd73bf3bc6ae86c5e76 (fixed)

Vendor states this is fixed in 3334ab72cbba55a632f24579cd47c4a4e5e69cda (fixed)

Vendor states this is fixed in 4067f4fa0423a89fb19a30b57231b384d77d2610 (fixed)

Vendor states this is fixed in 8f0abb39c16e719129de10596b3ae3363fa178b4 (fixed)

Vendor states this is fixed in a23d6029e730f8a151b1a34afb169baac1274583 (fixed)

Vendor states this is fixed in bc00d211da4ffad5314a2043b50bdc8ff8a33724 (fixed)

Vendor states this is fixed in c7630935d9a4986e8c0ed91658a781b7a77d73f7 (fixed)

Vendor states this is fixed in f921335123f6620c3dce5c96fbb95f18524a021c (fixed)

Vendor states this is fixed in 4.15 (unaffected)

Vendor states this is fixed in 5.10.227 (unaffected)

Vendor states this is fixed in 5.15.168 (unaffected)

Vendor states this is fixed in 5.4.285 (unaffected)