CVE-2024-53201

What it actually does

Null pointer dereference when pipe_ctx->plane_state is accessed without a prior null check in dcn20_program_pipe and dcn20_update_dchubp_dpp paths of the AMD display driver.

Why it matters to the business

Unpatched Linux systems using affected AMD GPUs may experience unexpected kernel crashes or display instability, leading to downtime and potential data loss for users and organizations relying on those kernels.

How an attack unfolds

An attacker with local access crafts display configuration sequences that cause pipe_ctx to be passed with a null plane_state into dcn20_update_dchubp_dpp, where direct attribute accesses trigger the dereference and kernel fault.

How to fix it

Update the Linux kernel to the fixed commit 0dd3ee31125508cd67f7e7172247f05b7fd1753a or later mainline versions that include the additional null checks in dcn20_program_pipe and related functions.

How to confirm the fix worked

Verify the presence of the null checks for plane_state in dcn20_program_pipe and dcn20_update_dchubp_dpp after applying the patch; confirm kernel build includes the fix commit and test display configuration workloads.

Typical attack path

1. Obtain local code execution or user privileges on a vulnerable Linux system
2. Trigger specific AMD display driver paths involving plane state updates
3. Pass pipe_ctx structures with null plane_state into dcn20_program_pipe
4. Cause kernel panic or denial of service via the missing null check

How to detect it

Review kernel logs for null pointer dereference oops in amd/display dcn20_program_pipe or dcn20_update_dchubp_dpp; correlate with recent display configuration changes or user-initiated graphics operations.

What your security team should do

• Prioritize kernel updates to the fixed commit on all AMD GPU systems
• Monitor for kernel oops or panic logs related to amd display code
• Apply updates before the next scheduled maintenance window given public disclosure