CVE-2024-49890

What it actually does

Null pointer dereference in drm/amd/pm when fw_info is unexpectedly null, leading to kernel crash or undefined behavior on affected AMD hardware.

Why it matters to the business

Potential denial of service on Linux systems with AMD GPUs or APUs; widespread kernel exposure across servers, desktops, and embedded devices increases operational risk of unplanned reboots and service disruption.

How an attack unfolds

An attacker with local access crafts or triggers a code path in the AMD power management firmware handling that returns null for fw_info; the kernel then dereferences the null value, causing a panic. Listed threat actors in 2024 zero-day and Linux kernel campaigns could chain this with other primitives for local DoS or limited privilege escalation on unpatched systems.

How to fix it

Update the Linux kernel to commit 29f388945770bd0a6c82711436b2bc98b0dfac92 or later. For Rocky Linux 8 wavpack packages, upgrade to version 5.1.0-15.el8 or newer. Reboot after installation and verify the running kernel contains the null-check fix.

How to confirm the fix worked

Confirm the installed kernel contains commit 29f388945770bd0a6c82711436b2bc98b0dfac92 or the equivalent distribution backport; inspect the drm/amd/pm source for the fw_info null guard; run targeted power-management stress tests on AMD hardware to ensure no dereference occurs.

Typical attack path

1. Obtain local user access on a vulnerable Linux system with AMD display hardware
2. Trigger the specific amd/pm firmware info retrieval path that can return null
3. Force dereference of the null fw_info pointer
4. Induce kernel panic or system instability

How to detect it

Review kernel logs for oops or panic messages referencing amd/pm or fw_info null dereference; correlate with process activity that exercises display power management on AMD hardware; check for presence of threat actor tooling associated with listed 2024 Linux kernel campaigns.

What your security team should do

• Prioritize kernel updates on all AMD-equipped Linux systems within standard change windows
• Monitor EPSS and threat actor reporting for any rise in exploitation attempts
• Apply the exact fixed package versions listed for each distribution
• Test the update in a staging environment before broad deployment