drm/xe: don't WARN on kernel job timeout when device already wedged
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.57, 7.2.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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)
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5a2f117a80c207372513ca8964eeb178874f4990 · fixed in 041cce629a08d4a2f1a28ec61a105b26b7f047e6; From 5a2f117a80c207372513ca8964eeb178874f4990 · fixed in 24d81b72992006f9c390f1fc85c7f991e6d06fd6; From 5a2f117a80c207372513ca8964eeb178874f4990 · fixed in 13087ad7817e6e5f210064518bfc4d6d58a9c2f3
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.6