If you use MSI Dragon Centrer or MSI Center, update them to see if the system file has been fixed.
The MSI Center takes optimization to the next level with easily adjustable system modes and resources for a wide range of scenarios and needs.
www.msi.com
MSI Center is competing for the title of "Worst OEM app (going strong again ASUS - so would strongly recommend against installing it). While Dragon Center - despite covering a bigger number of MSI laptops/PCs - there's also different versions - design for a specific model (if using the public version on this models - one would loose access to specific functions - like battery control & calibration). MSI Driver and App center - can point to the "functioning" version:
Driver & App Center is an useful tool that can help you keep your MSI applications and drivers up to date.
apps.microsoft.com
...but unless his PC/Laptop was released recently - tough chances for an Update (even for security updates - you have to ask them for an update - if using slightly older products).
----
Anyway the WinIo library - was not designed by MSI, it's simply adapted to their own software (
quite poorly - use to cause BSOD with earlier versions) The drivers triggering this issue - seem to be based on this vulnerability:
Vulnerable Driver WinIo64.sys in ITE IO Access - 1.0.0.0
Many vulnerability exists in driver WinIo64.sys, which allows low-privileged users read and write arbitary i/o port via specially crafted IOCTL requests. This can be exploited for privilege escalation, code execution under high privileges, and information disclosure. These signed drivers can also be used to bypass the Microsoft driver-signing policy to deploy malicious code.
version
1.0.0.0
Vulnerability causes
WinIo64.sys provides the functionality of read/write I/O ports, but it does not restrict the privileges of the caller, resulting in low-privileged users being able to call the driver and execute corresponding functions through DeviceIoControl.
Contribute to heyheysky/vulnerable-driver development by creating an account on GitHub.
github.com
----
Have a WinIo64.sys signed in 2018 - which does not trigger any warning. So, not sure... but i think - eSet is ussing above CVE-2024-55407/CVE-2024-55407_Winio64.sys vulnerability as referal - maybe not making a difrence betwen the diffrent versions.
It's also used by NiceHash (: cryptocurrency broker and exchange with an open marketplace for buyers and sellers of hashing power).