CVE-2024-49899

What it actually does

Uninitialized denominator variables in the AMD display driver (drm/amd/display) can remain zero, resulting in divide-by-zero faults during calculations.

Why it matters to the business

Potential kernel crashes or instability on Linux systems with AMD GPUs can cause unplanned downtime and operational disruption across many deployments due to the Linux kernel's widespread use.

How an attack unfolds

An attacker with local access triggers display code paths that leave denominators uninitialized at zero, leading to divide-by-zero exceptions and system instability. Referenced in contexts of espionage and financially motivated actors exploiting similar Linux kernel resource and bounds issues.

How to fix it

Apply kernel updates containing commit 9be768f08b16f020da376538b08463ac3a2ce8cd. For Rocky Linux 8 packages update exiv2 to 0:0.27.2-5.el8, gegl to 0:0.2.0-39.el8, gnome-color-manager to 0:3.28.0-3.el8, and libgexiv2 to 0:0.10.8-4.el8.

How to confirm the fix worked

Verify presence of commit 9be768f08b16f020da376538b08463ac3a2ce8cd in the running kernel or confirm updated package versions via package manager queries.

Typical attack path

1. Obtain local access to a Linux system with AMD display hardware
2. Invoke graphics or display operations that exercise uninitialized denominator paths
3. Force divide-by-zero condition in kernel driver
4. Trigger kernel panic or denial of service

How to detect it

Review kernel logs for divide-by-zero oops or panic entries originating from drm/amd/display code paths; correlate with process activity involving display or graphics initialization.

What your security team should do

• Prioritize kernel updates containing the referenced commit across all Linux deployments
• Apply Rocky Linux package fixes for affected components
• Monitor EPSS and threat actor reports for any increase in exploitation activity
• Test patches in staging environments before broad rollout given the kernel's ecosystem prevalence