drm/xe/guc: Fix stack_depot usage
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
drm/xe/guc: Fix stack_depot usage
Add missing stack_depot_init() call when CONFIG_DRM_XE_DEBUG_GUC is enabled to fix the following call stack:
[] BUG: kernel NULL pointer dereference, address: 0000000000000000 [] Workqueue: drm_sched_run_job_work [gpu_sched] [] RIP: 0010:stack_depot_save_flags+0x172/0x870 [] Call Trace: [] <TASK> [] fast_req_track+0x58/0xb0 [xe]
(cherry picked from commit 64fdf496a6929a0a194387d2bb5efaf5da2b542f)
From the CVE record · Linux
The Linux kernel’s drm/xe/guc code can hit a NULL pointer dereference when CONFIG_DRM_XE_DEBUG_GUC is enabled because stack_depot is not initialized. The input does not establish whether an attacker can trigger it, or any required access or user interaction.
Engineers running Linux kernels with CONFIG_DRM_XE_DEBUG_GUC enabled should check their kernel; affected versions are not specified.