CVE-2025-38356

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/xe/guc: Explicitly exit CT safe mode on unwind<br /> <br /> During driver probe we might be briefly using CT safe mode, which<br /> is based on a delayed work, but usually we are able to stop this<br /> once we have IRQ fully operational. However, if we abort the probe<br /> quite early then during unwind we might try to destroy the workqueue<br /> while there is still a pending delayed work that attempts to restart<br /> itself which triggers a WARN.<br /> <br /> This was recently observed during unsuccessful VF initialization:<br /> <br /> [ ] xe 0000:00:02.1: probe with driver xe failed with error -62<br /> [ ] ------------[ cut here ]------------<br /> [ ] workqueue: cannot queue safe_mode_worker_func [xe] on wq xe-g2h-wq<br /> [ ] WARNING: CPU: 9 PID: 0 at kernel/workqueue.c:2257 __queue_work+0x287/0x710<br /> [ ] RIP: 0010:__queue_work+0x287/0x710<br /> [ ] Call Trace:<br /> [ ] delayed_work_timer_fn+0x19/0x30<br /> [ ] call_timer_fn+0xa1/0x2a0<br /> <br /> Exit the CT safe mode on unwind to avoid that warning.<br /> <br /> (cherry picked from commit 2ddbb73ec20b98e70a5200cb85deade22ccea2ec)