I remember years ago there was a firmware source leak (or maybe the binary was analyzed or something) for gigabyte’s led controller firmware/drivers that basically just exposed the firmware programming bus to user land because that’s how they did lighting updates and the kernel mode driver just passed whatever the user mode driver gave it, which could include firmware updates to other hardware IDs.
It was at this point that I stopped running a lot of those hardware control utilities (and I suspect that might also be why I barely saw any issues with the Radeon 5700 XT that was a bit infamous for “its” issues that I think might have just been incompatibilities with 3rd party “helper” utilities or shit written by companies that had gotten to the “just ship it” stage of development).
I remember years ago there was a firmware source leak (or maybe the binary was analyzed or something) for gigabyte’s led controller firmware/drivers that basically just exposed the firmware programming bus to user land because that’s how they did lighting updates and the kernel mode driver just passed whatever the user mode driver gave it, which could include firmware updates to other hardware IDs.
It was at this point that I stopped running a lot of those hardware control utilities (and I suspect that might also be why I barely saw any issues with the Radeon 5700 XT that was a bit infamous for “its” issues that I think might have just been incompatibilities with 3rd party “helper” utilities or shit written by companies that had gotten to the “just ship it” stage of development).
Imagine if ransomware did a BYOVD and held your actual hardware ransom.
Shit like that should never have been signed by Microsoft, let alone made it through developer review at Gigabyte.