HID: synchronize input before cleaning up a failed probe
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c849a6143bec520aff2a6646518b0d041402428b · < 01eeb601a1626e683fb7b77c63f442b06fb87093| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel HID probe failure path can free driver resources while a report callback is still running, causing a use-after-free. This requires a probe to fail while a report is in progress; the input does not specify whether exploitation requires local or network access, authentication, or user interaction.
Engineers running Linux kernels with HID support should check their deployments; affected versions are not specified.