aboutsummaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
diff options
context:
space:
mode:
authorJeremy Cline <jcline@redhat.com>2021-01-11 16:05:28 -0500
committerAlex Deucher <alexander.deucher@amd.com>2021-01-13 23:46:34 -0500
commit0257b464b4d52a43cca6c8020b9586b2a6f46153 (patch)
treed5964f13a008c06b419e05ccf11c14764825abdf /drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c
parent9882e278536e6a78a49506aa70318db0455b5d74 (diff)
downloadlinux-0257b464b4d52a43cca6c8020b9586b2a6f46153.tar.gz
linux-0257b464b4d52a43cca6c8020b9586b2a6f46153.tar.bz2
linux-0257b464b4d52a43cca6c8020b9586b2a6f46153.zip
drm/amdkfd: Fix out-of-bounds read in kdf_create_vcrat_image_cpu()
KASAN reported a slab-out-of-bounds read of size 1 in kdf_create_vcrat_image_cpu(). This occurs when, for example, when on an x86_64 with a single NUMA node because kfd_fill_iolink_info_for_cpu() is a no-op, but afterwards the sub_type_hdr->length, which is out-of-bounds, is read and multiplied by entries. Fortunately, entries is 0 in this case so the overall crat_table->length is still correct. Check if there were any entries before de-referencing sub_type_hdr which may be pointing to out-of-bounds memory. Fixes: b7b6c38529c9 ("drm/amdkfd: Calculate CPU VCRAT size dynamically (v2)") Suggested-by: Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by: Jeremy Cline <jcline@redhat.com> Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_virt.c')
0 files changed, 0 insertions, 0 deletions