CVE-2024-26729

What it actually does

Null pointer dereference in dc_dmub_srv_cmd_list_queue_execute() and dc_dmub_srv_is_hw_pwr_up() when dc_dmub_srv is dereferenced before null check in AMD display driver.

Why it matters to the business

Potential system instability or crashes on affected Linux systems with AMD GPUs; low exploitation likelihood reduces immediate operational risk despite widespread kernel use.

How an attack unfolds

An attacker would need to trigger code paths calling these functions with a null dc_dmub_srv pointer, which is difficult to achieve remotely without specific hardware and driver state conditions.

How to fix it

Update to fixed kernel versions addressing the null checks; for listed Alpine packages upgrade openldap to 2.4.50-r2.

How to confirm the fix worked

Confirm updated kernel or package versions; review source for null checks preceding dereferences in dc_dmub_srv.c.

Typical attack path

1. Identify system running vulnerable AMD display driver code
2. Craft conditions to invoke dc_dmub_srv functions with null pointer
3. Trigger dereference to cause kernel panic or undefined behavior

How to detect it

Review kernel logs for null pointer dereference oops in display or amdgpu modules; check for unusual calls to dc_dmub_srv functions.

What your security team should do

• Prioritize kernel updates on AMD GPU systems given published fix
• Monitor EPSS and KEV status for any increase in activity
• Apply listed openldap package updates where applicable