CVE-2026-74699: drm/xe: Fix memory leak in exec_queue_set_hang_replay_state()
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Fix memory leak in execqueuesethangreplaystate()
The q->replaystate is blindly overwritten, which can potentially leak memory that was previously allocated by vmemdupuser(). Return an error if q->replaystate is not empty.
Discovered using AI-assisted static analysis confirmed by Intel Product Security.
(cherry picked from commit f6b6cc1118bdbc4265fa8b3bdf8565b26f13e56e)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1 - Upgrade
Upgrade
Linux kernel drm/xeto a version that resolves this vulnerability.Patch f6b6cc1118bdbc4265fa8b3bdf8565b26f13e56e
Event History
Frequently Asked Questions
What condition triggers the memory leak?
The leak can occur when exec_queue_set_hang_replay_state() is called while q->replay_state already contains an allocated replay state. The previous allocation, which may have come from vmemdup_user(), is overwritten without being released.
What does the fix change?
The fix rejects attempts to set the hang replay state when q->replay_state is already non-empty. This prevents overwriting the existing pointer and leaking its associated memory.
How can I determine whether a kernel contains the fix?
Check whether the kernel source includes the change that returns an error when q->replay_state is already set in exec_queue_set_hang_replay_state(). The issue was cherry-picked from commit f6b6cc1118bdbc4265fa8b3bdf8565b26f13e56e, and stable references are provided for commits 410596743958fbddeb845ff3efe2645397d7c7e2 and c5f500161709f27719701334190dff2325868ef0.