Look up another CVE · open CVE-2026-93189 in the interactive tracker
CVE-2026-93189
HID: core: quiesce input in hid_hw_stop() to prevent use-after-free
Published 2026-09-17 (31 days ago) by the Linux kernel CNA. Subsystem drivers/hid. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-93189 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixedDLA-4841-1 · 2026-10-17 · text | 6.1.190-1 | Update the kernel and reboot. DLA-4841-1 shipped the fix on 2026-10-17, in 6.1.190-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/hid/hid-core.c
- What this is
- HID CORE LAYERMAINTAINERS section matched on drivers/hid/ · linux-input@vger.kernel.org · Maintained
- Kernel module
- hid
Check it on the machine
grep -wE 'CONFIG_HID|CONFIG_HID_SUPPORT' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w hidPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on arm64/cloud-arm64
- trixieBnot built on arm64/cloud-arm64
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- bookworm · linux-6.12Mnot built on arm64/cloud-arm64
- M
- a module where it is built at all; some flavours do not build it
- B
- built in on some, a module on others, absent on the rest
- Build switches
- CONFIG_HID, CONFIG_HID_SUPPORT
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-09-17 (31 days ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.31%, higher than 22.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/hid
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 0 | 5.10.270 | 0744cb9520aa |
| 0 | 5.15.221 | c876c437d188 |
| 0 | 6.1.188 | 6787f1828f56 |
| 0 | 6.6.157 | 92cca302a4ea |
| 0 | 6.12.110 | 02246d8b462f |
| 0 | 6.18.52 | 544ebb25bd58 |
| 0 | 7.2.6 | 0fecd89f979a |
| 0 | 7.3 | a4bc41504690 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4841-1 | 2026-10-17 | bookworm 6.1.190-1 | tracker |
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:AAttack vector, adjacent network
- HIDP interrupt payloads racing hid_hw_stop() enter via hidp_recv_intr_frame() -> hidp_process_report() -> hid_input_report() -> hid_report_raw_event() -> hidraw_report_event(). nintendo_hid_probe() matches HID_BLUETOOTH_DEVICE Joy-Con/Pro IDs after hidp_session_dev_add()->hid_add_device(), so those reports come from a radio-adjacent HIDP peer.
- AC:LAttack complexity, low
- After hid_device_io_start() in nintendo_hid_probe(), the peer fails joycon_init() (joycon_read_info() or joycon_set_report_mode()) so err_close calls hid_hw_stop() without hid_device_io_stop(), and concurrently sends HIDP_TRANS_DATA|HIDP_DATA_RTYPE_INPUT frames so hidraw_report_event() runs during hidraw_disconnect(); the attacker drives both sides.
- PR:NPrivileges required, none
- hid_device_probe() binds the HID device with no host uid or capability check. A Bluetooth HID peripheral delivering hidp interrupt frames needs no Linux account; CAP_NET_ADMIN is only for bluetoothd HIDPCONNADD, not for the reporting device.
- UI:NUser interaction, none
- hidp_session_dev_work() calls hidp_session_dev_add()->hid_add_device(), which runs nintendo_hid_probe() automatically; after hid_device_io_start(), the peer's interrupt reports and the probe-fail hid_hw_stop() path need no victim open, mount, or click.
- S:UScope, unchanged
- The use-after-free is of host-kernel struct hidraw inside hid_hw_stop()->hid_disconnect()->hidraw_disconnect()->drop_ref(); it does not cross a VM, IOMMU, or sandbox boundary.
- C:HConfidentiality impact, high
- hid_report_raw_event() can enter hidraw_report_event() and take hidraw->list_lock on the object already kfree'd by drop_ref() from hid_hw_stop()'s hidraw_disconnect(), a use-after-free reusable for an arbitrary kernel read.
- I:HIntegrity impact, high
- The same freed hidraw is written from hidraw_report_event() (list_lock, kmemdup into list buffers, wake_up_interruptible on hidraw->wait) and can be sprayed, yielding an arbitrary write or control-flow hijack primitive.
- A:HAvailability impact, high
- hidraw_report_event() taking the freed hidraw->list_lock or waking hidraw->wait after drop_ref()'s kfree oopses or panics the kernel even when the UAF is not fully exploited.