CVE-2026-89624: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-xwr6-736m-c3p5
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-89624 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-89624 at a Glance

CVE Identifier CVE-2026-89624
GHSA Identifier GHSA-xwr6-736m-c3p5
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-89624

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-89624, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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>

References

NVD — CVE-2026-89624 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-89624
git.kernel.org/stable/c/01d9874e84... WEB
https://git.kernel.org/stable/c/01d9874e84d3ab78fd212ad822412eb3af84497f
git.kernel.org/stable/c/519fa26695... WEB
https://git.kernel.org/stable/c/519fa26695b02870022fcdc651efb3d379abe54e
git.kernel.org/stable/c/c457bb516b... WEB
https://git.kernel.org/stable/c/c457bb516b61edeab940235a011928e26925381e
git.kernel.org/stable/c/ce08c5555c... WEB
https://git.kernel.org/stable/c/ce08c5555cabcd444d8b77fa69a7cb68bb05f611

Frequently Asked Questions

What is CVE-2026-89624?
CVE-2026-89624 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-89624?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-89624?
CVE-2026-89624 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-89624?
CVE-2026-89624 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89624?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xwr6-736m-c3p5",
  "modified" : "2026-09-21T15:31:36Z",
  "published" : "2026-09-11T21:31:34Z",
  "aliases" : [ "CVE-2026-89624" ],
  "details" : "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>",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89624"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/01d9874e84d3ab78fd212ad822412eb3af84497f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/519fa26695b02870022fcdc651efb3d379abe54e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c457bb516b61edeab940235a011928e26925381e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ce08c5555cabcd444d8b77fa69a7cb68bb05f611"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:19:47Z"
  }
}