Quick answers
- Is CVE-2026-93248 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93248 being exploited in the wild.
- How severe is CVE-2026-93248?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Linux kernel 5.0 and later.
- Is there a fix for CVE-2026-93248?
- A patch was published on 2026-08-20. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93248 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-93248?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A logic flaw in xe_guc_submit.c's guc_exec_queue_timedout_job() function causes it to treat expected timeouts as unexpected warnings when killed execution queues are being torn down on a wedged device. The timeout handler skips calling guc_submit_hint_wedged() for killed queues, leaving the 'wedged' flag false even though the device is already in a wedged state, triggering a spurious WARN macro.
Affected products
- Linux kernel 5.0 and later
Timeline
- 2026-09-24: disclosed
- 2026-08-20: patched