Look up another CVE · open CVE-2026-90329 in the interactive tracker
CVE-2026-90329
HID: synchronize input before cleaning up a failed probe
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-90329 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
hid_device_io_start() allows reports to run concurrently with probe. If the probe subsequently fails, __hid_device_probe() releases driver resources and clears hdev->driver without first excluding those report callbacks. For example, a report may enter hidraw_report_event() while the failure path frees the associated hidraw object, leading to a use-after-free when the report takes the object's list lock. Stop input before performing failed-probe cleanup. This reacquires driver_input_lock and waits for any report callback already in progress.
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.34%, higher than 26.4% 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 |
|---|---|---|
| 3.10 | 5.10.270 | 3ffb088a2ed3 |
| 3.10 | 5.15.221 | 2c35cdeb13a0 |
| 3.10 | 6.1.188 | 98201b46f7e3 |
| 3.10 | 6.6.157 | 9a3da56aae28 |
| 3.10 | 6.12.110 | edd490b8ad85 |
| 3.10 | 6.18.52 | 01eeb601a162 |
| 3.10 | 7.2.6 | b85d1000eb88 |
| 3.10 | 7.3 | 207853d46f7e |
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
- HID input reports that race __hid_device_probe() cleanup after hid_device_io_start() arrive from an adjacent Bluetooth HID peer via hidp_recv_intr_frame() → hidp_process_report() → hid_input_report(). nintendo_hid_probe() for HID_BLUETOOTH_DEVICE Joy-Con/Pro calls hid_hw_start(HID_CONNECT_HIDRAW) then hid_device_io_start() before joycon_init() can fail.
- AC:LAttack complexity, low
- The attacker device both fails probe after hid_device_io_start() (nintendo joycon_init(), or mcp2221 mcp_set_i2c_speed() returning error with io still started) and sends interrupt reports so hidraw_report_event() runs on another CPU while hid_close_report()/hidraw_disconnect() free the object; both sides of the race are attacker-driven.
- PR:NPrivileges required, none
- hid_device_probe() matches and probes the HID device with no host uid, capability, or user-namespace check. A Bluetooth HID peer needs no Linux account; CAP_NET_ADMIN is only required for bluetoothd HIDPCONNADD, not for the peripheral to deliver hidp interrupt frames.
- UI:NUser interaction, none
- hidp_session_dev_work() calls hid_add_device(), which runs hid_device_probe() automatically once the HIDP session exists; after hid_device_io_start(), interrupt reports are processed with no victim open, mount, or other action (pairing is an attacker prerequisite, not exploit-time UI).
- S:UScope, unchanged
- The use-after-free is of host-kernel hidraw and hid_report objects inside HID core cleanup; 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 an object already freed by hidraw_disconnect()/hid_close_report() in the failed-probe path, a use-after-free that can be reused for an arbitrary kernel read.
- I:HIntegrity impact, high
- The same freed hidraw/hid_report object is written (list_lock, kmemdup into list buffers) and can be sprayed, yielding an arbitrary write or control-flow hijack primitive from the in-flight report callback.
- A:HAvailability impact, high
- hidraw_report_event() taking the freed hidraw->list_lock, or hid_get_report() walking reports already freed by hid_close_report(), oopses or panics the kernel even when the UAF is not fully exploited.