drm/xe/vm: Fix BO prefetch with CONSULT_MEM_ADVISE_PREF_LOC
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.18.447.1.67.2In the Linux kernel, the following vulnerability has been resolved:
drm/xe/vm: Fix BO prefetch with CONSULT_MEM_ADVISE_PREF_LOC
When prefetch region is DRM_XE_CONSULT_MEM_ADVISE_PREF_LOC for a BO VMA, the code used it as an index into region_to_mem_type[], causing an out-of-bounds access since the value is -1.
Resolve the preferred location for BO VMAs directly: local VRAM on dGFX (using the BO's tile placement) or system memory on iGPU.
Discovered using AI-assisted static analysis confirmed by Intel Product Security.
v2: -Fix null dereference
(cherry picked from commit d9a4906ac03be9f6ed3f3b45c56c866b867fd75b)
From the CVE record · Linux
The Linux kernel’s drm/xe/vm code can use a BO prefetch value of -1 as an index, causing an out-of-bounds access. An attacker may be able to trigger that access, but the input does not establish whether this requires local access, authentication, or user interaction.
Engineers running Linux kernels with the affected drm/xe/vm code should check their kernel version; affected versions are not specified.