---
id: CVE-2026-89624
title: |-
  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 initiali…
summary: |-
  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 initiali…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-825
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= f45f26a6b3e7260c129c7c6bb0ace63aeb7b3868 <
    519fa26695b02870022fcdc651efb3d379abe54e
  - >-
    Linux >= f06bf8d94fffbb544b1cb5402c92e0a075f0d420 <
    01d9874e84d3ab78fd212ad822412eb3af84497f
  - >-
    Linux >= f06bf8d94fffbb544b1cb5402c92e0a075f0d420 <
    c457bb516b61edeab940235a011928e26925381e
  - >-
    Linux >= f06bf8d94fffbb544b1cb5402c92e0a075f0d420 <
    ce08c5555cabcd444d8b77fa69a7cb68bb05f611
  - Linux c1fde337b317f0a226de92803288741c30799eb0
  - Linux af9f2471dfe5a48384f5b7f021a673fbc741465e
  - Linux b797352954eee6dc084cfaed0659dea60adfb484
  - Linux >= 6.12.24 < 6.12.111
  - Linux >= 6.6.88 < 6.7
  - Linux >= 6.13.12 < 6.14
  - Linux >= 6.14.3 < 6.15
  - Linux 6.15
published: '2026-09-11'
updated: '2026-09-21'
sourceUpdated: '2026-09-21T14:17:24.103'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-89624'
references:
  - url: 'https://git.kernel.org/stable/c/01d9874e84d3ab78fd212ad822412eb3af84497f'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/519fa26695b02870022fcdc651efb3d379abe54e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c457bb516b61edeab940235a011928e26925381e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ce08c5555cabcd444d8b77fa69a7cb68bb05f611'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: >-
      https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89624.json
  - url: 'https://access.redhat.com/security/cve/CVE-2026-89624'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2532040'
  - url: 'https://www.cve.org/CVERecord?id=CVE-2026-89624'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-89624'
  - url: >-
      https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-89624.mbox
tags:
  - nvd
  - cve.org
  - csaf
  - vex
  - red-hat
  - score-dispute
epss: 0.0017
epssPercentile: 0.06744
scores:
  nvd: 7.8
  cna: 7.8
  vendor: 5.5
ingestedAt: '2026-09-14T15:23:07.474Z'
---

## Overview

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 <baul.lee@xbow.com>

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

## Vendor advisories

- **Red Hat VEX** · Moderate · updated 2026-09-14 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-89624.json)