CVE-2026-89624 - Vulnerability Details

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

Published: 2026-09-11

Score: 7.8 High

EPSS: < 1% Very Low

KEV: No

Impact:

Action:

Analysis

Impact

In Linux kernel HID universal‑pidff driver, a failure of force‑feedback initialization after the device is started causes the driver pointer to be cleared while the HID core does not revert the device start. The resulting /dev/hidraw character device remains open but points to freed kernel memory, and opening that device triggers a use‑ callback, allowing an attacker with local access to corrupt kernel memory and potentially execute arbitrary code or elevate privileges.

Affected Systems

All Linux systems that ship a kernel containing the universal‑pidff driver before the fix are affected. The vulnerability manifests when the HID device has no input reports or other conditions that force the force‑feedback init path to fail. No other vendors or products are listed in the CNA data. Affected distributions include any that have not yet applied the patch committed in commit 01d9874e84d3ab78fd212ad822412eb3af84497f.

Risk and Exploitability

The CVSS score of 7.8 indicates high severity while the EPSS score of < 1 % shows a historically low exploitation likelihood. The vulnerability is not in CISA KEV. Exploitation requires to open a surviving /dev/hidraw* entry; the use‑after‑free can be triggered by a crafted device that causes force‑feedback initialization to fail. Successful exploitation can lead to kernel memory corruption and local privilege escalation.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Linux

unaffected

Version	Status	Constraints
`f45f26a6b3e7260c129c7c6bb0ace63aeb7b3868`	affected	< 519fa26695b02870022fcdc651efb3d379abe54e
`f06bf8d94fffbb544b1cb5402c92e0a075f0d420`	affected	< 01d9874e84d3ab78fd212ad822412eb3af84497f
`f06bf8d94fffbb544b1cb5402c92e0a075f0d420`	affected	< c457bb516b61edeab940235a011928e26925381e
`f06bf8d94fffbb544b1cb5402c92e0a075f0d420`	affected	< ce08c5555cabcd444d8b77fa69a7cb68bb05f611
`c1fde337b317f0a226de92803288741c30799eb0`	affected	—
`af9f2471dfe5a48384f5b7f021a673fbc741465e`	affected	—
`b797352954eee6dc084cfaed0659dea60adfb484`	affected	—
`6.12.24`	affected	< 6.12.111
`6.6.88`	affected	< 6.7
`6.13.12`	affected	< 6.14
`6.14.3`	affected	< 6.15

Linux

affected

Version	Status	Constraints
`6.15`	affected	—
`0`	unaffected	< 6.15
`6.12.111`	unaffected	≤ 6.12.*
`6.18.50`	unaffected	≤ 6.18.*
`7.2.4`	unaffected	≤ 7.2.*
`7.3-rc1`	unaffected	≤ *

No data.

Vendor Product Confidence Versions

Linux

Linux Kernel

99%

Version	Status	Scheme	Platform
`[f06bf8d94fffbb544b1cb5402c92e0a075f0d420,01d9874e84d3ab78fd212ad822412eb3af84497f)`	affected	code_commit	—
`[f06bf8d94fffbb544b1cb5402c92e0a075f0d420,c457bb516b61edeab940235a011928e26925381e)`	affected	code_commit	—
`[f06bf8d94fffbb544b1cb5402c92e0a075f0d420,ce08c5555cabcd444d8b77fa69a7cb68bb05f611)`	affected	code_commit	—
`c1fde337b317f0a226de92803288741c30799eb0`	affected	code_commit	—
`f45f26a6b3e7260c129c7c6bb0ace63aeb7b3868`	affected	code_commit	—
`af9f2471dfe5a48384f5b7f021a673fbc741465e`	affected	code_commit	—
`b797352954eee6dc084cfaed0659dea60adfb484`	affected	code_commit	—
`[6.6.88,6.7)`	affected	semver	—
`[6.12.24,6.13)`	affected	semver	—
`[6.13.12,6.14)`	affected	semver	—
`[6.14.3,6.15)`	affected	semver	—

Linux

Linux Kernel

99%

Version	Status	Scheme	Platform
`6.15`	affected	semver	—
`[0,6.15)`	unaffected	semver	—
`[6.18.50,6.19.0)`	unaffected	semver	—
`[7.2.4,7.3.0)`	unaffected	semver	—
`[7.3-rc1,*]`	unaffected	generic	—

Found an issue or want to improve our Enrichment? You can suggest it directly by opening an issue on our dedicated GitHub repository .

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

Upgrade the kernel to a version that includes the patch for the universal‑pidff driver 01d9874e84d3ab78fd212ad822412eb3af84497f.
Disable or unload the universal‑pidff driver for the affected device to prevent the device from lingering after a failed initialization.
Restrict access to /dev/hidraw* devices by setting strict file permissions so that only privileged users can open them until a permanent fix is implemented.

Generated by OpenCVE AI on September 15, 2026 at 21:12 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source	ID	Title
Debian DSA	DSA-6528-1	linux security update

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.0017.

Key SSVC decision points have not yet been added.

References

Link	Providers
https://git.kernel.org/stable/c/01d9874e84d3ab78fd212ad822412eb3af84497f
https://git.kernel.org/stable/c/519fa26695b02870022fcdc651efb3d379abe54e
https://git.kernel.org/stable/c/c457bb516b61edeab940235a011928e26925381e
https://git.kernel.org/stable/c/ce08c5555cabcd444d8b77fa69a7cb68bb05f611
https://nvd.nist.gov/vuln/detail/CVE-2026-89624
https://www.cve.org/CVERecord?id=CVE-2026-89624

History

Mon, 21 Sep 2026 13:30:00 +0000

Type	Values Removed	Values Added
References		https://git.kernel.org/stable/c/519fa26695b02870022fcdc651efb3d379abe54e

Sun, 13 Sep 2026 06:45:00 +0000

Type	Values Removed	Values Added
Metrics	cvssV3_1 `{'score': 6.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H'}`	cvssV3_1 `{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}`

Sat, 12 Sep 2026 00:15:00 +0000

Type	Values Removed	Values Added
Weaknesses		CWE-825
References		https://nvd.nist.gov/vuln/detail/CVE-2026-89624 https://www.cve.org/CVERecord?id=CVE-2026-89624
Metrics	threat_severity `None`	cvssV3_1 `{'score': 6.3, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H'}` threat_severity `Moderate`

Fri, 11 Sep 2026 23:45:00 +0000

Type	Values Removed	Values Added
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 <baul.lee@xbow.com>
Title		HID: universal-pidff: stop the device when force-feedback init fails
First Time appeared		Linux Linux linux Kernel
CPEs		cpe:2.3:o:linux:linux_kernel::::::::
Vendors & Products		Linux Linux linux Kernel
References		https://git.kernel.org/stable/c/01d9874e84d3ab78fd212ad822412eb3af84497f https://git.kernel.org/stable/c/c457bb516b61edeab940235a011928e26925381e https://git.kernel.org/stable/c/ce08c5555cabcd444d8b77fa69a7cb68bb05f611

Subscriptions

Linux Linux Kernel

MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2026-09-11T19:45:21.438Z

Updated: 2026-09-21T13:14:36.086Z

Reserved: 2026-09-11T19:38:34.737Z

Link: CVE-2026-89624

Vulnrichment

No data.

NVD

Status : Received

Published: 2026-09-11T20:19:47.750

Modified: 2026-09-21T14:17:24.103

Link: CVE-2026-89624

Redhat

Severity : Moderate

Publid Date: 2026-09-11T19:45:21Z

Links: CVE-2026-89624 - Bugzilla

OpenCVE Enrichment

Updated: 2026-09-15T21:15:14Z

Weaknesses

CWE-825
Expired Pointer Dereference

Impact

Affected Systems

Risk and Exploitability

Tracking

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

Subscriptions

JSON object

JSON object

JSON object

JSON object

JSON object