Vulnerable driver "SK_WinRing0"

[NielsGx]

Just got this notification from Windows Defender:

Also no SKIF shows this, and I can't reinstall it

Can you remake this driver without the "vulnerability" ?
If not possible, is there a proper way to make Windows Defender shut up ? I tried to select allow but it still doesn't let me reinstall it 🤔

[Nicholas-Steel]

That's a false flag, likely triggered by heuristics. Several hardware monitoring tools, even those from major companies like Intel, rely upon it for low level hardware monitoring.

[Kaldaien]

It is correctly flagged, they do not know what you are going to do with the driver. It does poke a hole into various x86 instructions that have to run in kernel-mode.

They seem to have decided recently that this is no longer an acceptable driver. I do not know how to get rid of those messages, you may have to just give up CPU monitoring altogether using SK. It is a real shame that AMD/Intel do not provide WMI data to read the sensor values with their chipset drivers. It should be their responsibility to do that, and not require everyone who wants to read CPU hardware sensors to write their own driver code.

[Nicholas-Steel]

I meant a false flag in the context of its inclusion with Special K (and other popular tools that use it). Heuristics would be picking up that it can be used for nefarious purposes, not that it is being used for nefarious purposes.

These tools tend to unload the driver when they're closed, so any potential for abuse of the vulnerability ends when you finish with SK/other tools.

[Nicholas-Steel]

That's a false flag, likely triggered by heuristics. Several hardware monitoring tools, even those from major companies like Intel, rely upon it for low level hardware monitoring.

The same driver is also used by Steam, it was previously only in beta version of Steam but it's now left beta.