aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
diff options
context:
space:
mode:
authorArtem Sadovnikov <[email protected]>2025-07-01 14:40:17 +0000
committerAlex Williamson <[email protected]>2025-07-15 20:17:17 +0000
commitb3060198483bac43ec113c62ae3837076f61f5de (patch)
tree9d90f7b53bed93ea2ecd7ab0fc4a01bd9422f81a /drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
parentvfio/pci: Separate SR-IOV VF dev_set (diff)
downloadkernel-b3060198483bac43ec113c62ae3837076f61f5de.tar.gz
kernel-b3060198483bac43ec113c62ae3837076f61f5de.zip
vfio/mlx5: fix possible overflow in tracking max message size
MLX cap pg_track_log_max_msg_size consists of 5 bits, value of which is used as power of 2 for max_msg_size. This can lead to multiplication overflow between max_msg_size (u32) and integer constant, and afterwards incorrect value is being written to rq_size. Fix this issue by extending integer constant to u64 type. Found by Linux Verification Center (linuxtesting.org) with SVACE. Suggested-by: Alex Williamson <[email protected]> Signed-off-by: Artem Sadovnikov <[email protected]> Reviewed-by: Yishai Hadas <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Alex Williamson <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c')
0 files changed, 0 insertions, 0 deletions