CVE-2026-89624
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:
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.
Read full descriptionShow less
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>
Technical details traces, logs and code from the original report
if (ret) {
devres_release_group(&hdev->dev, hdev->devres_group_id);
hid_close_report(hdev);
hdev->driver = NULL;
}CVSS
- Version: 3.1
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Base score: 7.8
Exploitation probability (EPSS)
- Probability of exploitation in the next 30 days: 0.17%
- Percentile among all scored CVEs: 6
- Score date: 10/5/2026
EPSS (Exploit Prediction Scoring System, FIRST) estimates how likely a vulnerability is to be exploited in the wild within 30 days. It complements CVSS (impact) and CISA KEV (confirmed exploitation).
🎯 ATT&CK techniques
How this vulnerability is exploited and what the attacker gains, in MITRE ATT&CK terms.
- Exploitation
T1068Exploitation for Privilege Escalationprivilege escalation85 % - Primary impact
T1005Data from Local Systemcollection75 % - Secondary impact
T1499.004Application or System Exploitationimpact65 %
Vulnerabilidad local con acceso L (PR:L) que no requiere interacción del usuario (UI:N), permitiendo que un usuario con privilegios locales cause use-after-free escribiendo en memoria liberada tras abrir /dev/hidrawX, logrando corrupción de datos y potencial DoS.
Inferred by our analysis agent from the official description, CVSS vector and CWE, and checked by a supervisor. May contain errors.
🛡️ ATT&CK mitigations that cover these techniques
Affected technologies (1)
⚠ AI-inferred from the description — NVD hasn't analyzed this CVE yet, these aren't verified CPEs.
References
Raw JSON (NVD)
Show
{
"id": "CVE-2026-89624",
"cveTags": [],
"metrics": {
"cvssMetricV31": [
{
"type": "Secondary",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 7.8,
"attackVector": "LOCAL",
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"integrityImpact": "HIGH",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"availabilityImpact": "HIGH",
"privilegesRequired": "LOW",
"confidentialityImpact": "HIGH"
},
"impactScore": 5.9,
"exploitabilityScore": 1.8
}
]
},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "f45f26a6b3e7260c129c7c6bb0ace63aeb7b3868",
"lessThan": "519fa26695b02870022fcdc651efb3d379abe54e",
"versionType": "git"
},
{
"status": "affected",
"version": "f06bf8d94fffbb544b1cb5402c92e0a075f0d420",
"lessThan": "01d9874e84d3ab78fd212ad822412eb3af84497f",
"versionType": "git"
},
{
"status": "affected",
"version": "f06bf8d94fffbb544b1cb5402c92e0a075f0d420",
"lessThan": "c457bb516b61edeab940235a011928e26925381e",
"versionType": "git"
},
{
"status": "affected",
"version": "f06bf8d94fffbb544b1cb5402c92e0a075f0d420",
"lessThan": "ce08c5555cabcd444d8b77fa69a7cb68bb05f611",
"versionType": "git"
},
{
"status": "affected",
"version": "c1fde337b317f0a226de92803288741c30799eb0",
"versionType": "git"
},
{
"status": "affected",
"version": "af9f2471dfe5a48384f5b7f021a673fbc741465e",
"versionType": "git"
},
{
"status": "affected",
"version": "b797352954eee6dc084cfaed0659dea60adfb484",
"versionType": "git"
},
{
"status": "affected",
"version": "6.12.24",
"lessThan": "6.12.111",
"versionType": "semver"
},
{
"status": "affected",
"version": "6.6.88",
"lessThan": "6.7",
"versionType": "semver"
},
{
"status": "affected",
"version": "6.13.12",
"lessThan": "6.14",
"versionType": "semver"
},
{
"status": "affected",
"version": "6.14.3",
"lessThan": "6.15",
"versionType": "semver"
}
],
"programFiles": [
"drivers/hid/hid-universal-pidff.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.15"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.15",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.12.111",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/hid/hid-universal-pidff.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-11T20:19:47.750",
"references": [
{
"url": "https://git.kernel.org/stable/c/01d9874e84d3ab78fd212ad822412eb3af84497f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/519fa26695b02870022fcdc651efb3d379abe54e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/c457bb516b61edeab940235a011928e26925381e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ce08c5555cabcd444d8b77fa69a7cb68bb05f611",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: universal-pidff: stop the device when force-feedback init fails\n\nuniversal_pidff_probe() starts the device with hid_hw_start() and then, if\nforce-feedback initialisation fails, returns the error through a label that\nonly does \"return error\". The device is left started.\n\nThe HID core does not unwind on the driver's behalf. __hid_device_probe()\nreleases the devres group, closes the report and clears hdev->driver:\n\n\tif (ret) {\n\t\tdevres_release_group(&hdev->dev, hdev->devres_group_id);\n\t\thid_close_report(hdev);\n\t\thdev->driver = NULL;\n\t}\n\nThe hidraw character device that hid_hw_start() registered through\nhid_connect() is allocated with kzalloc() and added with cdev_device_add(),\nso it is not devres-managed and survives that. With hdev->driver NULL,\nhid_device_remove() skips hid_hw_stop() as well, because it only unwinds\nwhile a driver is still attached. The registration therefore outlives the\ndevice on both paths.\n\nOpening the surviving /dev/hidrawX writes into freed memory. KASAN reports\na use-after-free write from hidraw_open() -> hid_hw_open() -> the\ntransport's open callback, which takes a spinlock inside the freed object.\nA descriptor that carries a PID usage page and no input reports is enough:\nhidraw claims the device so hid_hw_start() succeeds, while hid->inputs\nstays empty so force-feedback init fails. The other failure returns in\nhid_pidff_init_with_quirks() - no output reports, an allocation failure,\npidff_init_fields(), pidff_check_autocenter(), an unusable effect count,\ninput_ff_create() - all reach the same label.\n\nStop the device on that path. hid-dr.c and hid-emsff.c, which start the\ndevice with the same HID_CONNECT_DEFAULT & ~HID_CONNECT_FF mask, already do\nthis. The two earlier gotos must keep returning without hid_hw_stop(),\nsince neither has a started device, so give the path that fails after the\nstart its own label.\n\nDiscovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>"
}
],
"lastModified": "2026-09-21T14:17:24.103",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}