amdgpu: validate offset_in_bo of drm_amdgpu_gem_va
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9f7eb5367d0001536c361bd1400e14521f854ff1 · < f015aadc0d973047f49526a127e900c488d4e425| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
amdgpu: validate offset_in_bo of drm_amdgpu_gem_va
This is motivated by OOB access in amdgpu_vm_update_range when offset_in_bo+map_size overflows.
v2: keep the validations in amdgpu_vm_bo_map v3: add the validations to amdgpu_vm_bo_map/amdgpu_vm_bo_replace_map rather than to amdgpu_gem_va_ioctl
From the CVE record · Linux
The Linux kernel's amdgpu mapping code did not adequately validate offset_in_bo. If offset_in_bo plus map_size overflows, amdgpu_vm_update_range can access memory out of bounds. The input does not specify access requirements or whether user interaction is needed.
Engineers running the Linux kernel with amdgpu should check their installations; affected versions are not specified.