CVE-2024-53132

What it actually does

The flaw triggers a drm_WARN due to missing outer runtime PM protection in xe_pm_runtime_get_noresume during guc_exec_queue_add_msg, guc_exec_queue_fini, xe_exec_queue_destroy, and xe_oa_release paths in the Xe driver.

Why it matters to the business

May produce kernel warnings and potential power management instability on systems with Intel Xe graphics, with limited operational impact given low exploitability and no known campaigns.

How an attack unfolds

An attacker would craft conditions to invoke Xe OA release and execution queue teardown without proper runtime PM guards, surfacing the warning; no public exploitation or specific threat actor usage is associated.

How to fix it

Apply the upstream fix from commit b107c63d2953907908fd0cafb0e543b3c3167b75 or update to a kernel containing the resolution; no specific package versions are provided beyond the general kernel patch.

How to confirm the fix worked

Confirm absence of the drm_WARN message 'Missing outer runtime PM protection' during Xe OA release and exec queue operations after applying the fix; review kernel dmesg for the stack trace involving xe_pm_runtime_get_noresume.

Typical attack path

1. Trigger Xe OA object creation and messaging via GPU workloads
2. Force execution queue destruction path
3. Invoke xe_oa_release without outer PM protection
4. Observe drm_WARN in kernel logs

How to detect it

Search kernel logs and dmesg for the string 'Missing outer runtime PM protection' along with the stack trace referencing xe_pm_runtime_get_noresume, guc_exec_queue_add_msg, and xe_oa_release.

• Missing outer runtime PM protection
• xe_pm_runtime_get_noresume+0x8d/0xa0
• guc_exec_queue_add_msg+0x28/0x130
• xe_oa_release+0x9c/0xc0

What your security team should do

• Prioritize kernel updates containing the Xe OA PM fix for affected Intel graphics systems
• Monitor kernel logs for the specific runtime PM warning
• Test graphics workloads post-update to verify warning elimination