Описание
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets
The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.
Make sure the stack and data offsets are aligned to the 32K TLB size.
Check that the FW microcode actually fits in the space that is reserved for it.
(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets
The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access.
Make sure the stack and data offsets are aligned to the 32K TLB size.
Check that the FW microcode actually fits in the space that is reserved for it.
(cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)
Связанные уязвимости
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access. Make sure the stack and data offsets are aligned to the 32K TLB size. Check that the FW microcode actually fits in the space that is reserved for it. (cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)
A flaw was found in the Linux kernel's `drm/amdgpu/vce1` component. The vulnerability arises from incorrect calculations of the VCE 1 firmware size and offsets, which could lead to an out-of-bounds access. This issue could potentially allow a local attacker to cause system instability or a denial of service (DoS) by manipulating the firmware handling.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vce1: Fix VCE 1 firmware size and offsets The VCPU BO contains the actual FW at an offset, but it was not calculated into the VCPU BO size. Subtract this from the FW size to make sure there is no out of bounds access. Make sure the stack and data offsets are aligned to the 32K TLB size. Check that the FW microcode actually fits in the space that is reserved for it. (cherry picked from commit c16fe59f622a080fc457a57b3e8f14c780699449)
In the Linux kernel, the following vulnerability has been resolved: d ...