CVE-2026-68358: hwmon: (nzxt-kraken3) Stop device IO before calling hid_hw_stop
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (nzxt-kraken3) Stop device IO before calling hidhwstop
Calling hidhwstop() does not stop the device IO. This results in a race condition between hidinputreport() and the point immediately following the execution of hiddeviceiostart() within the driver probe function. If the probe operation fails after "io start" has been initiated, this race condition will result in a UAF vulnerability.
Fix the problem by calling hiddeviceiostop() before calling hidhwstop().
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In the nzxt-kraken3 driver probe function, if hid_device_io_start() has been executed and the probe later fails after "io start", call hid_device_io_stop() immediately following hid_device_io_start() (before calling hid_hw_stop). This prevents a race between hid_input_report() and the device IO stop that could lead to a UAF vulnerability.
Linux kernel hid driver (hwmon: nzxt-kraken3) Probe error handling sequence = Call hid_device_io_stop() immediately before/around hid_hw_stop() (specifically, stop device IO before calling hid_hw_stop; call hid_device_io_stop() if probe fails after hid_device_io_start())
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68358?
CVE-2026-68358 has been assigned a risk score of 51.
How do I fix CVE-2026-68358?
To fix CVE-2026-68358, ensure that the device IO is properly stopped before calling hid_hw_stop in your code.
What systems are affected by CVE-2026-68358?
CVE-2026-68358 affects the Linux kernel specifically when dealing with the nzxt-kraken3 hardware monitoring drivers.
What type of vulnerability is CVE-2026-68358?
CVE-2026-68358 is classified as a race condition vulnerability.
When was CVE-2026-68358 published?
CVE-2026-68358 was published on August 10, 2026.