On 25.06.2018 20:37, Borislav Petkov wrote:
(..)
>> +break;
>> case 0x14:
>> max_size = F14H_MPB_MAX_SIZE;
>> break;
>> @@ -251,22 +239,41 @@ static bool verify_patch(u8 family, const u8 *buf,
>> size_t buf_size,
>> max_size =
On 25.06.2018 20:37, Borislav Petkov wrote:
(..)
>> +break;
>> case 0x14:
>> max_size = F14H_MPB_MAX_SIZE;
>> break;
>> @@ -251,22 +239,41 @@ static bool verify_patch(u8 family, const u8 *buf,
>> size_t buf_size,
>> max_size =
On Sat, Jun 23, 2018 at 12:33:24AM +0200, Maciej S. Szmigiero wrote:
> Previously, the AMD microcode update driver has only checked the indicated
> microcode patch size for patches for the currently running CPU family.
> Patches for other families had their size trusted without further
>
On Sat, Jun 23, 2018 at 12:33:24AM +0200, Maciej S. Szmigiero wrote:
> Previously, the AMD microcode update driver has only checked the indicated
> microcode patch size for patches for the currently running CPU family.
> Patches for other families had their size trusted without further
>
Previously, the AMD microcode update driver has only checked the indicated
microcode patch size for patches for the currently running CPU family.
Patches for other families had their size trusted without further
verification.
Introduce such check for all CPU families known to the driver so if we
Previously, the AMD microcode update driver has only checked the indicated
microcode patch size for patches for the currently running CPU family.
Patches for other families had their size trusted without further
verification.
Introduce such check for all CPU families known to the driver so if we
6 matches
Mail list logo
