CVE-2026-89624HID: universal-pidff: stop the device when force-feedback init fails

Description

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]>

Timeline

Scores

EPSS (exploitation in 30 days)

0.17% · top 93% of all CVEs (13 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

• Linux · Linux

  • affected c1fde337b317f0a226de92803288741c30799eb0 – < 66358f5789c9a7e28809985a83c01e6ad933849e
  • affected f45f26a6b3e7260c129c7c6bb0ace63aeb7b3868 – < 519fa26695b02870022fcdc651efb3d379abe54e
  • affected f06bf8d94fffbb544b1cb5402c92e0a075f0d420 – < 01d9874e84d3ab78fd212ad822412eb3af84497f
  • affected f06bf8d94fffbb544b1cb5402c92e0a075f0d420 – < c457bb516b61edeab940235a011928e26925381e
  • affected f06bf8d94fffbb544b1cb5402c92e0a075f0d420 – < ce08c5555cabcd444d8b77fa69a7cb68bb05f611
  • affected af9f2471dfe5a48384f5b7f021a673fbc741465e
  • affected b797352954eee6dc084cfaed0659dea60adfb484
  • affected 6.6.88 – < 6.6.160
  • affected 6.12.24 – < 6.12.111
  • affected 6.13.12 – < 6.14
  • affected 6.14.3 – < 6.15

• Linux · Linux

  • affected 6.15
  • unaffected < 6.15
  • unaffected 6.6.160 – ≤ 6.6.*
  • unaffected 6.12.111 – ≤ 6.12.*
  • unaffected 6.18.50 – ≤ 6.18.*
  • unaffected 7.2.4 – ≤ 7.2.*
  • unaffected 7.3 – ≤ *

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2026-76536 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-89624](https://cveledger.app/badge/CVE-2026-89624.svg)](https://cveledger.app/cve/CVE-2026-89624)

Record last updated 21 Oct 2026, 12:48 UTC.