CVE-2026-68383: drm/xe/guc: Keep scheduler timeline name alive
Greg Kroah-Hartman <[email protected]>
| Newsgroups | org.kernel.vger.linux-cve-announce |
|---|---|
| Message-ID | <2026081045-CVE-2026-68383-c228@gregkh> |
From: Greg Kroah-Hartman <[email protected]> Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/xe/guc: Keep scheduler timeline name alive The scheduler keeps a pointer to the timeline name, but q->name is freed with the exec queue while scheduler fences can still reference it. Store the name in struct xe_guc_exec_queue so it shares the scheduler's RCU-deferred lifetime. (cherry picked from commit 41075f0eb5dcbd3b065d15f15ef7bbe9315188e8) The Linux kernel CVE team has assigned CVE-2026-68383 to this issue. Affected and fixed versions =========================== Issue introduced in 6.17 with commit 6bd90e700b4285e6a7541e00f969cab0d696adde and fixed in 7.1.6 with commit 77fd62412431e8c80ef2ad61466bc76fe425f80a Issue introduced in 6.17 with commit 6bd90e700b4285e6a7541e00f969cab0d696adde and fixed in 7.2-rc4 with commit 299bc6d50b1bed7d1f408391736712f01a0855e2 Issue introduced in 6.12.43 with commit b17fcce70733c211cb5dabf54f4f9491920b1d92 Issue introduced in 6.15.11 with commit ba37807d08bae67de6139346a85650cab5f6145a Issue introduced in 6.16.2 with commit 683b0e397dad9f26a42dcacf6f7f545a77ce6c06 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-68383 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/gpu/drm/xe/xe_guc_exec_queue_types.h drivers/gpu/drm/xe/xe_guc_submit.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/77fd62412431e8c80ef2ad61466bc76fe425f80a https://git.kernel.org/stable/c/299bc6d50b1bed7d1f408391736712f01a0855e2