drm/xe/tracing: Fix a potential TP_printk UAF
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 |
|
|
6.12.166.13.46.14In the Linux kernel, the following vulnerability has been resolved:
drm/xe/tracing: Fix a potential TP_printk UAF
The commit afd2627f727b ("tracing: Check "%s" dereference via the field and not the TP_printk format") exposes potential UAFs in the xe_bo_move trace event.
Fix those by avoiding dereferencing the xe_mem_type_to_name[] array at TP_printk time.
Since some code refactoring has taken place, explicit backporting may be needed for kernels older than 6.10.
From the CVE record · Linux
The Linux kernel’s xe_bo_move trace event has a potential use-after-free when TP_printk dereferences the xe_mem_type_to_name[] array. The input does not specify how an attacker could trigger it, whether access or user interaction is required, or what an attacker could achieve.
Engineers running Linux kernels with drm/xe tracing should check their kernel; affected versions are not specified, and kernels older than 6.10 may need an explicit backport.