mikewinddale

Reputable
Dec 22, 2016
277
30
4,840
24
It looks like this flaw only affects APUs, and furthermore, only people who grant physical or administrative access to the system?

I've got a Gigabyte X470 with a Ryzen 7 2700X. The update for me won't be released until later this month. But it seems I don't have to worry, since I don't have an APU? And even if I had an APU, I've got a home desktop, and nobody but me has physical or administrative access. Correct?

Thanks.
 

CerianK

Distinguished
Nov 7, 2008
249
44
18,720
3
It looks like this flaw only affects APUs, and furthermore, only people who grant physical or administrative access to the system?

I've got a Gigabyte X470 with a Ryzen 7 2700X. The update for me won't be released until later this month. But it seems I don't have to worry, since I don't have an APU? And even if I had an APU, I've got a home desktop, and nobody but me has physical or administrative access. Correct?

Thanks.
You are correct. Always assess your current security, performance and stability situation prior to performing a BIOS update so that you can minimize risk on all fronts. Currently, applying a BIOS update is a reasonably safe process when deemed necessary, but history tells us that was not always the case. However, you may also have to consider how much effort you put into the settings, so that you can replicate that process.
 
Jul 9, 2020
2
0
10
0
Does this issue really require a microcode update to fix? That's much more significant an issue than an issue with the BIOS code.
 

ASK THE COMMUNITY