SummaryAI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. Generated 23 Oct 2026.
The Intel Ethernet Diagnostics Driver for Windows contains a flaw in its IQVW32.sys (before 1.3.1.0) and IQVW64.sys (before 1.3.1.0) drivers, caused by improper input validation of certain IOCTL calls. A local user with low privileges can exploit it by sending a crafted IOCTL request (using one of the codes 0x80862013, 0x8086200B, 0x8086200F, or 0x80862007) to crash the system or possibly run arbitrary code with kernel privileges, requiring no user interaction.
Official description · NVDSource dataSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. Copied from NVD.
(1) IQVW32.sys before 1.3.1.0 and (2) IQVW64.sys before 1.3.1.0 in the Intel Ethernet diagnostics driver for Windows allows local users to cause a denial of service or possibly execute arbitrary code with kernel privileges via a crafted (a) 0x80862013, (b) 0x8086200B, (c) 0x8086200F, or (d) 0x80862007 IOCTL call.
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown.Breakdown
81.7 / 100
Exploited
Yes, in CISA KEV
Reports
1
Tactics
3/15
How an attack unfolds
Based on MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. mappings. Select a step to see the evidence.
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 5 years after disclosure. Public exploit code (Exploit-DB) was available 2 years before disclosure.
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
3 TechniqueOne specific attacker behaviour in MITRE ATT&CK, such as T1190 “Exploit Public-Facing Application”. IDs with a dot, like T1059.004, are sub-techniques., grouped by TacticThe attacker’s goal at a stage of an attack in MITRE ATT&CK, such as Initial Access or Persistence. Each technique belongs to one or more tactics. in kill-chain order, 5 cited passagesAIAI-writtenWritten by a language model from the source data on this page. Not reviewed by a person.3
ExecutionTA0002
Command and Scripting InterpreterT1059Medium Confidence (technique links)How sure Patchfirst is that an ATT&CK technique applies to this CVE. High and medium links are shown by default; low ones come from early or generic mappings, text matching, or contradict the CVE’s details.
AI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. claude-haiku-5-5: arbitrary code execution at kernel level.AI mapping from the description · primary impact
arbitrary code execution at kernel level
possibly execute arbitrary code with kernel privileges via a crafted
Exploitation for Privilege EscalationT1068Medium Confidence (technique links)How sure Patchfirst is that an ATT&CK technique applies to this CVE. High and medium links are shown by default; low ones come from early or generic mappings, text matching, or contradict the CVE’s details.
AI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. claude-haiku-5-5: local user kernel driver IOCTL exploitation for privilege escalation; TRAM2 annotated sentence label.AI mapping from the description · how it is exploited
local user kernel driver IOCTL exploitation for privilege escalation; TRAM2 annotated sentence label
allows local users to cause a denial of service or possibly execute arbitrary code with kernel privileges
In addition to these loaders, the attacker also exploits CVE-2015-2291, an Intel driver vulnerability, to load a malicious driver designed to reduce the token integrity of Microsoft Defender.
The primary objective of this malware is to disable Microsoft Defender by deploying a malicious kernel mode driver (“bring your own vulnerable driver” or BYOVD method) via exploiting a vulnerable Intel driver (CVE-2015-2291) and then downloading and executing the third-stage payload.
Application or System ExploitationT1499.004Medium Confidence (technique links)How sure Patchfirst is that an ATT&CK technique applies to this CVE. High and medium links are shown by default; low ones come from early or generic mappings, text matching, or contradict the CVE’s details.
AI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. claude-haiku-5-5: crafted IOCTL crashes the kernel driver.AI mapping from the description · primary impact
0 rules for this CVE · 129 general rules for its techniques
Rules for this CVE
0Sigma ruleAn open, vendor-neutral detection rule for log data. Security teams convert Sigma rules into searches for their own SIEM. that reference CVE-2015-2291 directly.
CVE-specific rules are not available in this build. Search SigmaHQ ↗
General rules for this CVE’s techniques
These detect the technique in general, not this specific vulnerability.
Exploitation for Privilege EscalationT106831general rules
Named in 1 threat reportMachineMachine-matchedFound by keyword or pattern matching over threat-report text. Not reviewed by a person. Exact CVE id found in the report text.
1 reportTrend Micro
Reports are matched by finding the exact id CVE-2015-2291 in their text; nobody has reviewed the match. One passage is shown per report, at most 320 characters, linked to the original.
The primary objective of this malware is to disable Microsoft Defender by deploying a malicious kernel mode driver (“bring your own vulnerable driver” or BYOVD method) via exploiting a vulnerable Intel driver (CVE-2015-2291) and then downloading and executing the third-stage payload.