Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a BYOVD Attack?

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.

Illustration for the cybersecurity term BYOVD
Home / Blog / Cybersecurity Terms / What Is a BYOVD Attack?
17 November 2026

What Is a BYOVD Attack?

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.

Why Signed Drivers Are a Weak Point

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.

Cases That Shaped the Technique

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.

Where It Sits in the Attack

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.

Defences That Work

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.

FAQ – Frequently Asked Questions

Does BYOVD Need Administrator Rights?

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.

Is the Microsoft Driver Blocklist Enough?

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.

Why Are the Vulnerable Drivers Not Simply Revoked?

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.

How Would We Detect an EDR Killer?

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.

Related Terms

You May Be Interested In These

What Are the CIS Controls?

Cybersecurity Terms

17 November 2026

What Are the CIS Controls?

Read More
What Was the Mirai Botnet?

Cybersecurity Terms

17 November 2026

What Was the Mirai Botnet?

Read More
What Is TACACS+?

Cybersecurity Terms

17 November 2026

What Is TACACS+?

Read More