Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
In a Bring Your Own Vulnerable Driver attack, an intruder installs a legitimately signed but flawed kernel driver and exploits it to gain kernel privileges and disable endpoint security.

What Is a BYOVD Attack?
Bring Your Own Vulnerable Driver, usually shortened to BYOVD, is a technique in which an attacker who already has administrator rights on a Windows host installs a legitimate, correctly signed kernel driver that contains a known vulnerability, then exploits that vulnerability to execute code in the kernel. The driver is not malware. It is a real product, signed by a real vendor, and Windows loads it without complaint.
Kernel access is the prize. From ring 0, an attacker can terminate protected processes, strip the protection flags from endpoint agents, unhook kernel callbacks, hide files and processes, and read or write any memory on the system. It is the most direct route available for defeating an endpoint detection and response product that cannot otherwise be killed from user mode.
Since 64-bit Windows Vista, kernel drivers must be signed. The signature confirms who produced the driver, not whether the driver is safe. Thousands of drivers shipped with motherboards, overclocking utilities, backup products, anti-cheat engines, and even security software expose dangerous primitives — arbitrary physical memory read and write, arbitrary model-specific register access, or arbitrary process termination — through IOCTL interfaces reachable by any administrator.
Revoking a certificate breaks every legitimate product signed with it, so revocation is slow and rare. The result is a large, persistent, publicly catalogued inventory of weaponisable drivers. The community project LOLDrivers tracks over a thousand of them, with hashes and known exploitation details.
gdrv.sys, affected by CVE-2018-19320, to disable driver signature enforcement and then load its own unsigned driver that killed security software.RTCore64.sys from MSI Afterburner, affected by CVE-2019-16098, to read and write kernel memory and remove the callbacks used by more than a thousand EDR and antivirus drivers.dbutil_2_3.sys, CVE-2021-21551. A firmware update utility driver shipped on Dell systems since 2009, exposing arbitrary kernel read and write. It was adopted immediately by multiple intrusion sets after disclosure in May 2021.The technique is now standard in ransomware tooling, and dedicated utilities such as the various “EDR killer” builds are sold as a service component alongside the encryptor.
BYOVD is a defence evasion and privilege escalation step, not an entry point. It assumes the attacker already has local administrator, usually obtained through credential theft, an unpatched application, or an earlier escalation. That ordering matters for defenders: if administrator rights are rare and tightly controlled, BYOVD never gets its chance.
SeLoadDriverPrivilege, which administrators hold. Fewer local administrators means fewer opportunities.Testing whether your controls survive a driver-based evasion attempt is part of our SOC maturation services, because the detection that matters most here is noticing that a sensor stopped reporting.
Yes. Installing and starting a kernel driver requires the load driver privilege, which administrators hold and standard users do not. That makes BYOVD a post-compromise technique rather than an entry point. It also means that reducing the number of accounts with local administrator rights, and separating administrative from day-to-day accounts, directly reduces exposure to it.
It raises the cost significantly but is not complete. The list covers drivers Microsoft knows about, and new vulnerable drivers are published constantly by vendors who had no idea their utility exposed a kernel primitive. Combine the blocklist with memory integrity, application control in allow-list mode, restricted administrator rights, and detection on driver load events.
Revoking a code signing certificate invalidates every driver signed with it, including current, legitimate products from that vendor. The operational damage can be considerable, so revocation is used sparingly and usually after a vendor has reissued signed replacements. Microsoft’s blocklist is the compromise: it blocks specific driver versions without breaking the vendor’s wider signing.
Watch for kernel service creation events, new drivers loading on endpoints that do not normally change, and known vulnerable driver hashes. Equally important, alert on agent health: an endpoint that stops sending telemetry while still answering on the network has usually been silenced rather than switched off. Treat telemetry gaps as findings and investigate them within the hour.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.