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

> A local attacker can trigger a kernel warning and potential instability by causing a GPU job timeout on an already wedged Intel Xe device.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93248, DEBIAN-CVE-2026-93248, GHSA-h35v-9854-jq4c, UBUNTU-CVE-2026-93248

## What is CVE-2026-93248?

CVE-2026-93248 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

## Which versions are affected by CVE-2026-93248?


## How do I fix CVE-2026-93248?

Apply the vendor's patch.

## Is CVE-2026-93248 being exploited?

There is no known exploitation of CVE-2026-93248 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93248 and fix it if it is affected.

What it is: CVE-2026-93248 is a denial of service vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93248 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93248/ (Markdown: https://insights.sbomify.com/CVE-2026-93248/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93248
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93248
- OSV: https://osv.dev/vulnerability/CVE-2026-93248

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93248/
Summaries are generated and may contain mistakes; the official description above is the record.