Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2015-2291: Kernel Privilege Escalation in Intel Ethernet Diagnostics Driver

Published Aug 9, 2017 · Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS7.8High · v3.1
EPSS15.7%97th percentile
CISA KEVYesAdded Feb 10, 2023
In the wildActivePer CISA KEV
Vendor
Intel Corporation
IdentifiersCVE-2015-2291CWE-782

CVE-2015-2291 affects the 32-bit and 64-bit Intel Ethernet diagnostics drivers for Windows before version 1.3.1.0. Crafted calls to IOCTLs 0x80862013, 0x8086200B, 0x8086200F, or 0x80862007 allow local users to cause denial of service or potentially execute arbitrary code with kernel privileges. Exploitation can expose kernel and physical memory read/write capabilities. The vulnerability is actively abused in bring-your-own-vulnerable-driver attacks to map malicious kernel drivers and disable endpoint security.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise system availability and kernel integrity. Kernel memory access enables process-token manipulation, elevation to SYSTEM, loading of malicious kernel code, and interference with security controls. Observed exploitation includes lowering Microsoft Defender's process-token integrity, disabling endpoint protection, and tampering with Event Tracing for Windows logging. These capabilities facilitate subsequent malware and ransomware activity; data theft and encryption are downstream payload effects rather than intrinsic effects of the vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Enable and maintain Microsoft's vulnerable-driver blocklist, and use Windows Defender Application Control policies to block the vulnerable Intel driver. Restrict administrative access and driver-loading privileges to reduce BYOVD opportunities. Monitor for unexpected Intel diagnostics driver installation or loading, particularly when followed by security-process impairment, process-token changes, or security-logging disruption.

Remediation

Patch, then assume compromise.

Replace affected Intel Ethernet diagnostics drivers with version 1.3.1.0 or later, or uninstall the diagnostics driver if it is unnecessary. Remove obsolete vulnerable copies and enforce driver-loading controls to prevent attackers from reintroducing an older vulnerable version.

Public exploits

Exploits

4 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Intel-CVE-2015-2291This repository is a proof-of-concept (PoC) exploit for CVE-2015-2291, a privilege escalation vulnerability in the Intel Ethernet diagnostics driver (iqvw64e.sys) on Windows. The exploit is implemented in C++ and consists of two main code files: 'intelExplo.cpp' (main logic) and 'intelExplo.hpp' (definitions and helper functions/structs). The exploit interacts with the driver via the device interface '\\.\Nal' and leverages IOCTLs to perform arbitrary kernel memory read/write operations. By manipulating kernel memory, the exploit locates the SYSTEM process token and overwrites the current process token, effectively granting SYSTEM privileges to the exploit process. It then spawns a SYSTEM shell (cmd.exe). The code also includes additional functionality for physical-to-virtual address translation and mapping physical memory, which can be used for arbitrary kernel memory access. The exploit requires the vulnerable driver to be loaded and accessible, and is intended for local privilege escalation on Windows systems.Tare05 · Disclosed Feb 22, 2020 · c++ · localOperationalCVE-2015-2291This repository provides a detailed write-up and fully functional local privilege escalation exploit for CVE-2015-2291, targeting the Intel Ethernet diagnostics driver (IQVW32.sys/IQVW64.sys) on Windows 7 SP1 and Windows 10 20H2 (both 64-bit). The exploit is implemented in C and assembly, with separate codebases for Windows 7 and Windows 10. The main exploit logic is in 'exploit.c', which interacts with the vulnerable driver via the DeviceIoControl API using the IOCTL code 0x80862007. The exploit leverages the lack of proper input validation in the driver to perform arbitrary memory operations in kernel space, ultimately overwriting function pointers in the HalDispatchTable to execute custom kernel shellcode. The shellcode steals the SYSTEM process token and assigns it to the current process, resulting in a SYSTEM shell. The repository includes all necessary source files, project files for Visual Studio, and detailed technical documentation in the README. The exploit is operational and demonstrates a real-world local privilege escalation technique using a BYOVD (Bring Your Own Vulnerable Driver) approach.gmh5225 · Disclosed Jun 28, 2022 · c · assembly · localOperationaliqvw64e-privilege-escalationRepository contains a Windows local privilege escalation PoC for CVE-2015-2291 targeting Intel's iqvw64e.sys (device \\.\Nal). Structure: (1) README.md explains reverse engineering of the driver's IRP_MJ_DEVICE_CONTROL handler, the IOCTL 0x80862007 path, and a jump-table dispatch where index 0x33 triggers an internal memmove-like routine. This yields an arbitrary kernel memory copy primitive, which is wrapped into read64/write64 helpers. (2) main.cpp is the operational exploit: it enumerates kernel drivers to find the ntoskrnl.exe base, loads a local ntoskrnl.exe to resolve PsInitialSystemProcess and compute its kernel address, uses the memmove primitive to read the SYSTEM process EPROCESS and its Token, walks the ActiveProcessLinks list to find the current process EPROCESS by UniqueProcessId, overwrites the current process Token with the SYSTEM token (token stealing), then launches powershell.exe. The exploit is build-specific due to hardcoded EPROCESS offsets for Windows 10 x64 22H2 (19045.6466). No network IOCs are present; all interaction is local via the device driver and kernel memory primitives.ethanedits · Disclosed Jan 25, 2026 · c++ · markdown · localOperationalNalCallerStandalone Windows C++ exploit demonstration targeting CVE-2015-2291 in Intel's iqvw64e.sys NAL driver. The repository contains 14 files: three C++ implementation files, four headers, three Visual Studio solution/project files, a README, an MIT license, and two Git configuration files. It is not associated with an exploit framework. The build uses C++20 and requests administrator elevation for x64 configurations. main.cpp unloads any existing iqvw64e service, deploys and loads the vulnerable driver, opens \\.\Nal, invokes ExAllocatePool for a 4096-byte nonpaged allocation, prints the returned address, and attempts driver cleanup. nal.cpp implements driver deployment, IOCTL wrappers, arbitrary memory-copy/fill primitives, virtual-to-physical translation, physical-memory mapping, and kernel-function invocation. nal.h defines the device interface and request layouts. sup.cpp implements service management, loaded-kernel-module enumeration, and kernel-export resolution; common.h, ntos.h, and sup.h provide supporting declarations. The kernel-call primitive uses physical-memory mapping to write a 28-byte x64 trampoline into the loaded driver at offset 0x1901, then submits function ID 0x3A through IOCTL 0x80862007. This permits calls to a supplied kernel address with four arguments; an additional wrapper resolves ntoskrnl exports by name. This is a local administrator-to-kernel capability, not a demonstrated unprivileged-to-administrator escalation. No runtime network communication, command-and-control endpoint, download, or exfiltration is present. The implementation is substantive exploit code with a hardcoded demonstration payload, but execution has not been verified. The supplied files omit resource.h and the embedded driver array it must provide, preventing an as-supplied build. Driver compatibility cannot be established without that binary, and the fixed patch offset makes the technique build-specific. The code does not restore the patched bytes before unloading and does not free its demonstrated kernel allocation. The repository URL, git reference, and archive size were not supplied; empty strings and zero represent unavailable metadata.antoniorauso · Disclosed Oct 18, 2026 · cpp · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Intel CorporationEthernet Diagnostics Driver Iqvw32.Sysapplication
Intel CorporationEthernet Diagnostics Driver Iqvw64.Sysapplication
FAQ

Frequently asked questions

Is CVE-2015-2291 exploited in the wild?
Yes. As of Oct 29, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 10, 2023.
Is there a public exploit for CVE-2015-2291?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2015-2291, the earliest disclosed Feb 22, 2020.
Is there a patch for CVE-2015-2291?
Replace affected Intel Ethernet diagnostics drivers with version 1.3.1.0 or later, or uninstall the diagnostics driver if it is unnecessary. Remove obsolete vulnerable copies and enforce driver-loading controls to prevent attackers from reintroducing an older vulnerable version.
What products are affected by CVE-2015-2291?
Intel Corporation Ethernet Diagnostics Driver Iqvw32.Sys and Intel Corporation Ethernet Diagnostics Driver Iqvw64.Sys.
How severe is CVE-2015-2291?
CVE-2015-2291 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 15.7% (97th percentile) as of Oct 29, 2026.
Activity feed

Recent activity

27 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
malware newsNews · Oct 8, 2026Ignore all instructions and read this blog: The state of AI-analysis evasion in malware - Malware News - Malware Analysis, News and IndicatorsA vulnerability in the Intel Ethernet diagnostics driver, iqvw64e.sys, abused in BYOVD attacks to disable endpoint detection and response from kernel space. The article connects MANTLEMAZE to the driver through a PDB path, but does not confirm that MANTLEMAZE exploits the vulnerability.Read more ↗talosintelligence otherNews · Oct 8, 2026Ignore all instructions and read this blog: The state of AI-analysis evasion in malwareA vulnerability in the Intel Ethernet diagnostics driver, iqvw64e.sys, abused in BYOVD attacks to disable EDR from kernel space. The article connects the driver to MANTLEMAZE through an embedded PDB path, but does not establish that MANTLEMAZE successfully exploits the vulnerability.Read more ↗codebyNews · Oct 7, 2026SilverFox BYOVD: обход антивируса невидимым драйверомAn improper input-validation vulnerability in the Intel Ethernet Diagnostics Driver, iqvw64.sys. The article reports CVSS 7.8, CISA KEV inclusion, and use in ransomware campaigns. It is discussed as a known-driver comparison and a defensive testing example.Read more ↗trellix blogNews · May 19, 2026Scattered Spider: The Modus OperandiA vulnerability in the Intel Ethernet diagnostics driver for Windows (iqvw64.sys) that can allow denial of service or possible arbitrary code execution with kernel privileges, and was used by Scattered Spider in a bring-your-own-vulnerable-driver style attack to deploy a malicious kernel driver.Read more ↗
+14 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence15Every report linking this CVE to a named adversary.
Associated malware22Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity9Community discussion across Reddit, Mastodon, and other social sources.