CVE-2024-47729

What it actually does

The flaw creates a potential deadlock in the DRM/XE graphics driver when user bind operations map to fault-capable engines, because fault handling depends on bind completion which in turn depends on fault handling.

Why it matters to the business

Affected Linux systems with Intel Xe graphics hardware may experience kernel-level deadlocks resulting in system hangs or crashes, disrupting user sessions and workloads until reboot; the issue has low observed exploitation likelihood and no known ransomware usage.

How an attack unfolds

An attacker with local access on a faulting device issues crafted user bind operations that map to engines capable of page faults, triggering a circular wait between bind completion and fault resolution that deadlocks the reserved copy engine path.

How to fix it

Upgrade the Linux kernel to a version containing commit 439fc1e569c57669dbb842d0a77c7ba0a82a9f5d; for Rocky Linux 8 packages apply the listed fixed module versions for python-docutils, python-nose, python-pygments, python-PyMySQL, python36 and python-docs.

How to confirm the fix worked

Confirm the running kernel contains the referenced commit or later; exercise bind queue creation on faulting devices and verify no deadlock occurs; check package versions against the fixed module entries for Rocky Linux 8.

Typical attack path

1. Obtain local unprivileged access to a Linux system using an affected kernel with Xe graphics
2. Trigger graphics bind operations that exercise the user-bind-to-faulting-engine path
3. Induce the deadlock condition causing kernel hang

How to detect it

Review kernel logs for drm/xe messages indicating bind queue issues or engine faults; look for sudden system unresponsiveness correlated with graphics activity on Xe hardware.

What your security team should do

• Prioritize kernel package updates on all Xe-equipped systems
• Restrict unprivileged local access until patches are applied
• Monitor kernel logs for drm/xe bind or fault-related stalls