drm/xe: don't WARN on kernel job timeout when device already wedged
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 041cce629a08d4a2f1a28ec61a105b26b7f047e6, Kernel 13087ad7817e6e5f210064518bfc4d6d58a9c2f3 and Kernel 24d81b72992006f9c390f1fc85c7f991e6d06fd6.
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)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=5a2f117a80c207372513ca8964eeb178874f4990 <041cce629a08d4a2f1a28ec61a105b26b7f047e6, >=5a2f117a80c207372513ca8964eeb178874f4990 <13087ad7817e6e5f210064518bfc4d6d58a9c2f3, >=5a2f117a80c207372513ca8964eeb178874f4990 <24d81b72992006f9c390f1fc85c7f991e6d06fd6 | 041cce629a08d4a2f1a28ec61a105b26b7f047e6, 13087ad7817e6e5f210064518bfc4d6d58a9c2f3, 24d81b72992006f9c390f1fc85c7f991e6d06fd6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket