Local kernel crash via empty IOCTL buffer
Published Jun 17, 2026 · Updated Jun 17, 2026
NULL pointer dereference in the SignalRGB kernel driver before 1.3.7.0 allows local users to crash Windows via an empty IOCTL buffer. Seven IOCTL handlers in SignalIo.sys dereference SystemBuffer without validating caller-supplied buffer lengths, so zero input and output lengths leave the pointer NULL. Any authenticated local user able to open \.\SignalIo can repeatedly crash the Windows kernel, causing availability loss without reported data disclosure or modification.
Summary
What happened
NULL pointer dereference in the SignalRGB kernel driver before 1.3.7.0 allows local users to crash Windows via an empty IOCTL buffer. Seven IOCTL handlers in SignalIo.sys dereference SystemBuffer without validating caller-supplied buffer lengths, so zero input and output lengths leave the pointer NULL. Any authenticated local user able to open \.\SignalIo can repeatedly crash the Windows kernel, causing availability loss without reported data disclosure or modification.
The record
- CVE
- CVE-2026-8050
- Published
- Jun 17, 2026
- Updated
- Jun 17, 2026
- Vendor
- SignalRGB
- Product
- SignalRGB kernel driver
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 17, 2026CVE publishedPublication date reported by the CVE source.
- Jun 17, 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=0 <1.3.7.0
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.
Weakness, pattern, technique
No sourced classifications are available.
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