CVE-2024-53133

What it actually does

Allocation failure leaves dml contexts invalid; dc_state_copy_internal performs a shallow copy of those pointers, and subsequent release of the copied state triggers a double-free.

Why it matters to the business

Local attackers can crash or potentially execute code on affected Linux systems, leading to denial of service or privilege escalation on workstations and servers that use AMD display hardware.

How an attack unfolds

An attacker with local access triggers a dml allocation failure during state handling, forces dc_state_copy_internal to duplicate dangling pointers, then releases the new state to trigger the double-free and gain control or crash the kernel.

How to fix it

Update the Linux kernel to commit 874ff59cde8fc525112dda26b501a1bac17dde9f or later stable releases that contain the fix; rebuild and reboot affected systems.

How to confirm the fix worked

Confirm the running kernel contains commit 874ff59cde8fc525112dda26b501a1bac17dde9f; exercise display state allocation and copy paths under memory pressure to verify absence of the double-free condition.

Typical attack path

1. Obtain local user access on a vulnerable Linux system
2. Trigger dml allocation failure path in amd display driver
3. Cause dc_state_copy_internal to shallow-copy invalid dml context
4. Release the copied state to induce double-free
5. Leverage resulting memory corruption for code execution or denial of service

How to detect it

Review kernel logs for dml allocation failures followed by state copy and double-free warnings; inspect crash dumps for invalid dml pointer usage in dc_state_copy_internal paths.

What your security team should do

• Prioritize kernel updates on all AMD GPU systems within the next patch cycle
• Monitor for local privilege-escalation attempts targeting kernel display code
• Apply compensating controls such as mandatory access controls until patches are deployed