Answer in brief
CVE-2026-89624 records a Unknown severity vulnerability in HID: universal-pidff: stop the device when force-feedback init fails. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f06bf8d94fffbb544b1cb5402c92e0a075f0d420 <01d9874e84d3ab78fd212ad822412eb3af84497f || >=f06bf8d94fffbb544b1cb5402c92e0a075f0d420 <c457bb516b61edeab940235a011928e26925381e || >=f06bf8d94fffbb544b1cb5402c92e0a075f0d420 <ce08c5555cabcd444d8b77fa69a7cb68bb05f611 || c1fde337b317f0a226de92803288741c30799eb0 || f45f26a6b3e7260c129c7c6bb0ace63aeb7b3868 || af9f2471dfe5a48384f5b7f021a673fbc741465e || b797352954eee6dc084cfaed0659dea60adfb484 || >=6.6.88 <6.7 || >=6.12.24 <6.13 || >=6.13.12 <6.14 || >=6.14.3 <6.15 | 01d9874e84d3ab78fd212ad822412eb3af84497f, c457bb516b61edeab940235a011928e26925381e, ce08c5555cabcd444d8b77fa69a7cb68bb05f611, 6.7, 6.13, 6.14, 6.15 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: HID: universal-pidff: stop the device when force-feedback init fails universal_pidff_probe() starts the device with hid_hw_start() and then, if force-feedback initialisation fails, returns the error through a label that only does "return error". The device is left started. The HID core does not unwind on the driver's behalf. __hid_device_probe() releases the devres group, closes the report and clears hdev->driver: if (ret) { devres_release_group(&hdev->dev, hdev->devres_group_id); hid_close_report(hdev); hdev->driver = NULL; } The hidraw character device that hid_hw_start() registered through hid_connect() is allocated with kzalloc() and added with cdev_device_add(), so it is not devres-managed and survives that. With hdev->driver NULL, hid_device_remove() skips hid_hw_stop() as well, because it only unwinds while a driver is still attached. The registration therefore outlives the device on both paths. Opening the surviving /dev/hidrawX writes into freed memory. KASAN reports a use-after-free write from hidraw_open() -> hid_hw_open() -> the transport's open callback, which takes a spinlock inside the freed object. A descriptor that carries a PID usage page and no input reports is enough: hidraw claims the device so hid_hw_start() succeeds, while hid->inputs stays empty so force-feedback init fails. The other failure returns in hid_pidff_init_with_quirks() - no output reports, an allocation failure, pidff_init_fields(), pidff_check_autocenter(), an unusable effect count, input_ff_create() - all reach the same label. Stop the device on that path. hid-dr.c and hid-emsff.c, which start the device with the same HID_CONNECT_DEFAULT & ~HID_CONNECT_FF mask, already do this. The two earlier gotos must keep returning without hid_hw_stop(), since neither has a started device, so give the path that fails after the start its own label. Discovered by XBOW, triaged by Baul Lee <[email protected]>
Quoted source text, attributed separately from HOL analysis.