System crash via driver null pointer dereference
Published Aug 11, 2026 · Updated Aug 11, 2026
Null pointer dereference in Intel PROSet/Wireless WiFi Software for Windows before 24.10 allows remote attackers to crash systems. Intel identifies the affected locus only as Ring 2 device drivers and has not published the driver routine or input operation that reaches the null dereference. No privileges or user interaction are required, but the attacker needs adjacent-network access; successful exploitation interrupts the vulnerable system.
Summary
What happened
Null pointer dereference in Intel PROSet/Wireless WiFi Software for Windows before 24.10 allows remote attackers to crash systems. Intel identifies the affected locus only as Ring 2 device drivers and has not published the driver routine or input operation that reaches the null dereference. No privileges or user interaction are required, but the attacker needs adjacent-network access; successful exploitation interrupts the vulnerable system.
The record
- CVE
- CVE-2026-20878
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Intel Corporation
- Product
- Intel PROSet/Wireless WiFi Software for Windows
- Classifications
- CWE-476, T1499
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See references
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo