CVE-2026-90397: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-gcqw-f4ff-hx84
Published
Advisory Summary

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

CVE Identifier CVE-2026-90397
GHSA Identifier GHSA-gcqw-f4ff-hx84
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-90397

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-90397, 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: firmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published In qcom_scm_probe(), devm_request_threaded_irq() is called before smp_store_release(&__scm, scm). Two paths can dereference __scm before it is published, both causing a NULL pointer dereference. The IRQ handler receives scm via its data argument but passes only wq_ctx to qcom_scm_waitq_wakeup() and qcom_scm_get_completion(), which then dereference __scm directly. Thread scm through both functions so the IRQ handler path never touches __scm. Non-atomic SMC calls made during probe (e.g. from qcom_tzmem_init via qcom_scm_shm_bridge_enable) can return WAITQ_SLEEP, causing qcom_scm_wait_for_wq_completion() to run before __scm is published and dereference it. Add platform_set_drvdata(pdev, scm) early in probe and change qcom_scm_wait_for_wq_completion() to take the device pointer and use dev_get_drvdata() to reach scm, removing any dependency on __scm.

References

Frequently Asked Questions

What is CVE-2026-90397?
CVE-2026-90397 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-90397?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90397?
CVE-2026-90397 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90397?
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-gcqw-f4ff-hx84",
  "modified" : "2026-09-17T18:32:04Z",
  "published" : "2026-09-17T18:32:04Z",
  "aliases" : [ "CVE-2026-90397" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware: qcom: scm: Fix NULL dereference in IRQ handler before __scm is published\n\nIn qcom_scm_probe(), devm_request_threaded_irq() is called before\nsmp_store_release(&__scm, scm). Two paths can dereference __scm before\nit is published, both causing a NULL pointer dereference.\n\nThe IRQ handler receives scm via its data argument but passes only wq_ctx\nto qcom_scm_waitq_wakeup() and qcom_scm_get_completion(), which then\ndereference __scm directly. Thread scm through both functions so the IRQ\nhandler path never touches __scm.\n\nNon-atomic SMC calls made during probe (e.g. from qcom_tzmem_init via\nqcom_scm_shm_bridge_enable) can return WAITQ_SLEEP, causing\nqcom_scm_wait_for_wq_completion() to run before __scm is published and\ndereference it. Add platform_set_drvdata(pdev, scm) early in probe and\nchange qcom_scm_wait_for_wq_completion() to take the device pointer and\nuse dev_get_drvdata() to reach scm, removing any dependency on __scm.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90397"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1d753df5899ec356272d08bc4718e82844e4bdf0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/966d23c7e68ea32679275a7e3d2383181002c868"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b451f38cb7f5bca78484362347f039c08c94de95"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f312ef5026678f14caf1378c5f7fffdf667f9c81"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:39Z"
  }
}