CVE-2026-90363: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-356c-wqmf-cf5h
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-90363
GHSA Identifier GHSA-356c-wqmf-cf5h
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-90363

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-90363, 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: drm/msm: don't tear down KMS twice when KMS init fails When priv->kms_init() (mdp4_kms_init() / mdp5_kms_init()) fails partway through, both display drivers already tear their KMS state down via mdp4_destroy() / mdp5_kms_destroy() before returning the error. The common error path in msm_drm_init() then runs msm_drm_uninit() -> msm_drm_kms_uninit(), which tries to destroy the very same KMS a second time, which causes a use-after-free crash. Bring MDP4/MDP5 in line with the DPU driver whose dpu_kms_init() doesn't perform error cleanup on the failure. Let the common path own the cleanup, instead of freeing the KMS from their error paths. The crash trace for the reference: __lock_acquire from lock_acquire (kernel/locking/lockdep.c:5906 kernel/locking/lockdep.c:5863) lock_acquire from touch_wq_lockdep_map (kernel/workqueue.c:4094 (discriminator 1)) touch_wq_lockdep_map from __flush_workqueue (kernel/workqueue.c:4136) __flush_workqueue from msm_drm_kms_uninit (drivers/gpu/drm/msm/msm_kms.c:243 (discriminator 33)) msm_drm_kms_uninit from msm_drm_uninit (drivers/gpu/drm/msm/msm_drv.c:93) msm_drm_uninit from msm_drm_init (drivers/gpu/drm/msm/msm_drv.c:184) msm_drm_init from try_to_bring_up_aggregate_device (drivers/base/component.c:249 drivers/base/component.c:227) try_to_bring_up_aggregate_device from __component_add (drivers/base/component.c:269 drivers/base/component.c:748) __component_add from dsi_host_attach (drivers/gpu/drm/msm/dsi/dsi_host.c:1739) dsi_host_attach from mipi_dsi_attach (drivers/gpu/drm/drm_mipi_dsi.c:383) mipi_dsi_attach from sharp_nt_panel_probe (drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c:247) Patchwork: https://patchwork.freedesktop.org/patch/742068/

References

NVD — CVE-2026-90363 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90363
git.kernel.org/stable/c/08827aa40f... WEB
https://git.kernel.org/stable/c/08827aa40f0ee9d37dcff8d6acb340b970051486
git.kernel.org/stable/c/93c125e4ea... WEB
https://git.kernel.org/stable/c/93c125e4ea98fb25f927ba5a334d85845127d667
git.kernel.org/stable/c/e2a99fa93b... WEB
https://git.kernel.org/stable/c/e2a99fa93b400dfbb9598103249f71969501094a

Frequently Asked Questions

What is CVE-2026-90363?
CVE-2026-90363 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-90363?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90363?
CVE-2026-90363 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90363?
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-356c-wqmf-cf5h",
  "modified" : "2026-09-17T18:32:02Z",
  "published" : "2026-09-17T18:32:02Z",
  "aliases" : [ "CVE-2026-90363" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm: don't tear down KMS twice when KMS init fails\n\nWhen priv->kms_init() (mdp4_kms_init() / mdp5_kms_init()) fails partway\nthrough, both display drivers already tear their KMS state down via\nmdp4_destroy() / mdp5_kms_destroy() before returning the error. The\ncommon error path in msm_drm_init() then runs msm_drm_uninit() ->\nmsm_drm_kms_uninit(), which tries to destroy the very same KMS a second\ntime, which causes a use-after-free crash.\n\nBring MDP4/MDP5 in line with the DPU driver whose dpu_kms_init() doesn't\nperform error cleanup on the failure. Let the common path own the\ncleanup, instead of freeing the KMS from their error paths.\n\nThe crash trace for the reference:\n\n  __lock_acquire from lock_acquire (kernel/locking/lockdep.c:5906 kernel/locking/lockdep.c:5863)\n  lock_acquire from touch_wq_lockdep_map (kernel/workqueue.c:4094 (discriminator 1))\n  touch_wq_lockdep_map from __flush_workqueue (kernel/workqueue.c:4136)\n  __flush_workqueue from msm_drm_kms_uninit (drivers/gpu/drm/msm/msm_kms.c:243 (discriminator 33))\n  msm_drm_kms_uninit from msm_drm_uninit (drivers/gpu/drm/msm/msm_drv.c:93)\n  msm_drm_uninit from msm_drm_init (drivers/gpu/drm/msm/msm_drv.c:184)\n  msm_drm_init from try_to_bring_up_aggregate_device (drivers/base/component.c:249 drivers/base/component.c:227)\n  try_to_bring_up_aggregate_device from __component_add (drivers/base/component.c:269 drivers/base/component.c:748)\n  __component_add from dsi_host_attach (drivers/gpu/drm/msm/dsi/dsi_host.c:1739)\n  dsi_host_attach from mipi_dsi_attach (drivers/gpu/drm/drm_mipi_dsi.c:383)\n  mipi_dsi_attach from sharp_nt_panel_probe (drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c:247)\n\nPatchwork: https://patchwork.freedesktop.org/patch/742068/",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90363"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/08827aa40f0ee9d37dcff8d6acb340b970051486"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/93c125e4ea98fb25f927ba5a334d85845127d667"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e2a99fa93b400dfbb9598103249f71969501094a"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:35Z"
  }
}