Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
IOCTL delivery is inherently local (AV:L), trivially triggered with an empty buffer (AC:L), requires a local handle to the driver typically open to standard users (PR:L), and impact is availability-only kernel crash.
Primary rating from Vendor (certcc).
CVSS VectorVendor: certcc
Lifecycle Timeline
4DescriptionCVE.org
In SignalRGB versions prior to 1.3.7.0, seven of the thirteen IOCTL handlers dereference the SystemBuffer pointer without first verifying that it is non-NULL. Sending an IOCTL with an empty input buffer causes a NULL pointer dereference, resulting in a kernel crash.
AnalysisAI
Local denial-of-service in the SignalRGB kernel driver (versions prior to 1.3.7.0) allows any process able to open a handle to the driver to crash the Windows kernel by sending an IOCTL with an empty input buffer. Seven of thirteen IOCTL handlers dereference the SystemBuffer pointer without a NULL check, producing a bugcheck (BSOD). No public exploit identified at time of analysis, EPSS is 0.14%, and a vendor patch is available.
Technical ContextAI
SignalRGB is RGB lighting control software whose Windows kernel-mode driver (cpe:2.3:a:signalrgb:signalrgb_kernel_driver) exposes an IOCTL interface to its user-mode service. When a driver uses METHOD_BUFFERED I/O, the I/O Manager populates Irp->AssociatedIrp.SystemBuffer with the caller-supplied data; if the input length is zero, that pointer can be NULL. The root cause is a CWE-476 NULL Pointer Dereference: seven of the driver's thirteen IOCTL dispatch routines read from SystemBuffer before validating it is non-NULL, so dereferencing the unmapped low-address page in kernel context triggers a KMODE_EXCEPTION_NOT_HANDLED bugcheck. The flaw was coordinated through the CERT/CC (VU#380058).
RemediationAI
Vendor-released patch: SignalRGB 1.3.7.0 - upgrade all hosts running SignalRGB to 1.3.7.0 or later as documented in CERT/CC VU#380058 (https://kb.cert.org/vuls/id/380058). If immediate patching is not possible, the most effective compensating control is to stop and disable the SignalRGB kernel driver service (sc stop / sc config start=disabled) which will eliminate the attack surface at the cost of losing RGB lighting control, or to uninstall SignalRGB on shared/multi-user systems where untrusted local users could trigger the crash. Tightening the driver device object's DACL via a third-party tool to restrict DeviceIoControl access to SYSTEM/Administrators is theoretically possible but fragile and not recommended over patching.
More in Signalrgb Kernel Driver
View allSame technique Denial Of Service
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-37804
GHSA-wm74-h69m-r7vv