CVE-2026-68361

hwmon: (corsair-psu) Stop device IO before calling hid_hw_stop

N/A

Published: August 10, 2026 at 12:03 PM UTC

Updated: August 19, 2026 at 05:20 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: hwmon: (corsair-psu) Stop device IO before calling hid_hw_stop hid_hw_stop() does not stop the device IO. This results in a race condition between hid_input_report() and the point immediately following the execution of hid_device_io_start() within corsairpsu_probe(). If the probe operation fails after "io start" has been initiated, this race condition will result in a uaf vulnerability [1]. CPU0 CPU1 ==== ==== corsairpsu_probe() hid_device_io_start() ... unlock driver_input_lock hid_hw_stop() kfree(hidraw) __hid_input_report() ... acquire driver_input_lock hid_report_raw_event() hidraw_report_event() ... access hidraw's list_lock // trigger uaf Consequently, when corsairpsu_probe() fails and hid_hw_stop() needs to be executed, the io_started flag is first cleared while holding the driver_input_lock to prevent potential race conditions involving input reports. [1] BUG: KASAN: slab-use-after-free in rt_spin_lock+0x83/0x400 kernel/locking/spinlock_rt.c:56 Call Trace: hidraw_report_event+0x5d/0x3a0 drivers/hid/hidraw.c:577 hid_report_raw_event+0x311/0x1730 drivers/hid/hid-core.c:2076 __hid_input_report drivers/hid/hid-core.c:2152 [inline] hid_input_report+0x44e/0x580 drivers/hid/hid-core.c:2174 hid_irq_in+0x47e/0x6d0 drivers/hid/usbhid/hid-core.c:286 __usb_hcd_giveback_urb+0x3b3/0x5e0 drivers/usb/core/hcd.c:1657 dummy_timer+0x8a9/0x47d0 drivers/usb/gadget/udc/dummy_hcd.c:2005 Allocated by task 10: hidraw_connect+0x57/0x430 drivers/hid/hidraw.c:606 hid_connect+0x5bf/0x19d0 drivers/hid/hid-core.c:2277 hid_hw_start+0xa8/0x120 drivers/hid/hid-core.c:2387 corsairpsu_probe+0xd9/0x3c0 drivers/hwmon/corsair-psu.c:782 Freed by task 10: hidraw_disconnect+0x4f/0x60 drivers/hid/hidraw.c:662 hid_disconnect drivers/hid/hid-core.c:2362 [inline] hid_hw_stop+0x101/0x1e0 drivers/hid/hid-core.c:2407 corsairpsu_probe+0x327/0x3c0 drivers/hwmon/corsair-psu.c:826 Fix the problem by calling hid_device_io_stop() before calling hid_hw_stop(). [groeck: Updated subject and description; call hid_device_io_stop() only if IO has been started]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.11 ≤ v < 5.15.2165.11 ≤ v < 6.1.1835.11 ≤ v < 6.12.1015.11 ≤ v < 6.18.425.11 ≤ v < 6.6.1485.11 ≤ v < 7.1.65.11 ≤ v < 7.25.11d115b51e0e567199c821fc39e13b6af7e78f247d

Vendor states this is fixed in 45dcd8a63069197f64dbda30509b9e224b74c0d8 (fixed)

Vendor states this is fixed in 9ab8656548cd737b98d0b19c4253aff8d68e97f4 (fixed)

Vendor states this is fixed in bb25bd980f2d9bd34558e1b1d16636e4945baf14 (fixed)

Vendor states this is fixed in c0aae8d24f5e52d6910f97d59bc624e131f3ae1a (fixed)

Vendor states this is fixed in c80ed058f31bb0251a748034d69feb376741dcb2 (fixed)

Vendor states this is fixed in e6e1e0f3050d1a1a3ea1c9d6253363e87fdad67a (fixed)

Vendor states this is fixed in ec477af3a7e8d3964e62fd24ef01cdebb96b8e4e (fixed)

Vendor states this is fixed in 5.11 (unaffected)

Vendor states this is fixed in 5.15.216 (unaffected)

Vendor states this is fixed in 6.1.183 (unaffected)

Vendor states this is fixed in 6.12.101 (unaffected)

Vendor states this is fixed in 6.18.42 (unaffected)