Note that an OEM implementation of a video chipset may mean that some vulnerabilities in the public unified driver might not impact an OEM implementation - for example, in Surface the implementation of Optimus graphics on Book and Book2 means that the Nvidia drivers are customized and do not implement the entire stack - which also means that using the public driver can cause issues the inbox driver does not. Same thing with Intel or onboard AMD graphics - implementations that aren't reference can mean only use the OEMs driver to avoid adding issues where they don't exist. Again, a Surface example is apropos here: on a Surface, the Intel or nVidia GPU drivers know how to read the calibration information for the panel, and will adjust their function accordingly for output. Direct-from-the-vendor public drivers from their respective sites *do not* read that calibration, and thus aren't as accurate and may also cause increased TDR failures and bugchecks.
Always check with the system manufacturer to ask about exposure to vulnerabilities, and when they will be providing an updated version if affected. Also, what (if anything) may happen if they use a vendor-supplied driver versus the one the system manufacturer is providing.
