CVE-2026-92482: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-6wqp-4g53-5h3x
Published
Advisory Summary

CVE-2026-92482 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-92482 at a Glance

CVE Identifier CVE-2026-92482
GHSA Identifier GHSA-6wqp-4g53-5h3x
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-92482

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-92482, 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: pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip The gpio_chip is allocated with device-managed memory but registered with the non-managed gpiochip_add_data(). This was harmless while the drivers were built-in, but once they can be built as modules and unbound/rmmod'd, devm frees the gpio_chip's memory while it is still registered, causing a use-after-free. Register it with devm_gpiochip_add_data() so it shares the same device-managed lifecycle, which also lets the manual gpiochip_remove() error paths go away.

References

Frequently Asked Questions

What is CVE-2026-92482?
CVE-2026-92482 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-92482?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-92482?
CVE-2026-92482 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-92482?
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-6wqp-4g53-5h3x",
  "modified" : "2026-10-15T12:30:51Z",
  "published" : "2026-09-17T18:32:06Z",
  "aliases" : [ "CVE-2026-92482" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip\n\nThe gpio_chip is allocated with device-managed memory but registered with\nthe non-managed gpiochip_add_data(). This was harmless while the drivers\nwere built-in, but once they can be built as modules and unbound/rmmod'd,\ndevm frees the gpio_chip's memory while it is still registered, causing a\nuse-after-free.\n\nRegister it with devm_gpiochip_add_data() so it shares the same\ndevice-managed lifecycle, which also lets the manual gpiochip_remove()\nerror paths go away.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92482"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/01b5fcdc30c0ab35af960b60508eae1f7f7d32fd"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9c650317ba553d297f3fc5f0ae40ec53d86f9dab"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b8fa1098ee9f627d38bdf7c0ef6c1a6058a4165b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:50Z"
  }
}