CVE-2026-89732: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-95m6-h3qf-8pc2
Published
Advisory Summary

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

CVE-2026-89732 at a Glance

CVE Identifier CVE-2026-89732
GHSA Identifier GHSA-95m6-h3qf-8pc2
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-89732

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-89732, 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: usb: gadget: f_fs: Prevent deadlock during ep0 read loop Currently, ffs_ep0_read() holds ffs->mutex when it prepares to go to sleep waiting for an event. When no setup events are pending, it calls wait_event_interruptible_exclusive_locked_irq() with the mutex still held. The wait macro deliberately drops the waitqueue spinlock before sleeping but does not drop the mutex. If a userspace daemon is polling ep0 via read() and the gadget is asynchronously torn down via configfs (e.g., echo "" > UDC), a deadlock can occur: 1. The configfs teardown calls functionfs_unbind(), which queues a FUNCTIONFS_UNBIND event. 2. The daemon wakes up, consumes the event, and drops the mutex. 3. However, if the daemon loops and immediately issues another read() before exiting, it reacquires ffs->mutex and again goes into an interruptible sleep. 4. Meanwhile, functionfs_unbind() continues execution and attempts to acquire ffs->mutex to tear down ep0req. 5. The kernel deadlocks because the configfs thread is stuck in an uninterruptible sleep waiting for the mutex, while the userspace daemon is in an interruptible sleep holding the mutex forever because no more events will arrive. To fix this, we drop both the waitqueue spinlock and ffs->mutex before going to sleep, and use wait_event_interruptible_exclusive() instead. Upon waking up, we jump back to the `retry` label to safely reacquire the mutex and re-evaluate the state machine. By not sleeping with ffs->mutex held, we natively decouple gadget teardowns (which require the mutex) from userspace polling.

References

Frequently Asked Questions

What is CVE-2026-89732?
CVE-2026-89732 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-89732?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-89732?
CVE-2026-89732 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-89732?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-95m6-h3qf-8pc2",
  "modified" : "2026-09-14T15:32:35Z",
  "published" : "2026-09-11T21:31:38Z",
  "aliases" : [ "CVE-2026-89732" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: f_fs: Prevent deadlock during ep0 read loop\n\nCurrently, ffs_ep0_read() holds ffs->mutex when it prepares to go to\nsleep waiting for an event. When no setup events are pending, it calls\nwait_event_interruptible_exclusive_locked_irq() with the mutex still\nheld. The wait macro deliberately drops the waitqueue spinlock before\nsleeping but does not drop the mutex.\n\nIf a userspace daemon is polling ep0 via read() and the gadget is\nasynchronously torn down via configfs (e.g., echo \"\" > UDC), a\ndeadlock can occur:\n\n1. The configfs teardown calls functionfs_unbind(), which queues a\n   FUNCTIONFS_UNBIND event.\n2. The daemon wakes up, consumes the event, and drops the mutex.\n3. However, if the daemon loops and immediately issues another read()\n   before exiting, it reacquires ffs->mutex and again goes into an\n   interruptible sleep.\n4. Meanwhile, functionfs_unbind() continues execution and attempts to\n   acquire ffs->mutex to tear down ep0req.\n5. The kernel deadlocks because the configfs thread is stuck in an\n   uninterruptible sleep waiting for the mutex, while the userspace\n   daemon is in an interruptible sleep holding the mutex forever\n   because no more events will arrive.\n\nTo fix this, we drop both the waitqueue spinlock and ffs->mutex before\ngoing to sleep, and use wait_event_interruptible_exclusive() instead.\nUpon waking up, we jump back to the `retry` label to safely reacquire\nthe mutex and re-evaluate the state machine. By not sleeping with\nffs->mutex held, we natively decouple gadget teardowns (which require\nthe mutex) from userspace polling.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-89732"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/30430509c156e1df2bdafd5f1cadb160e53db5d6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/34e88f53614640b59039a46717fb6142e9871022"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/569dd7e5dcffe1e1c6b26ca2cd3be57eb433e082"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b0a6bfac0c3c3edf5b2ecaee87a09234601fe78d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bafddd0f20b5228760be303aa69c58502e92309c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/eac233e63f9db82ba874e3cccafaafab162999e0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fbe3db4b650c284df8eb4cb68eebcf270cf861b5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fd20cc68bbdb5620696ac108e8f2efd180fe2c1a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-11T20:20:03Z"
  }
}