CVE-2026-90429: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-fc4x-65xv-jwjh
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-90429
GHSA Identifier GHSA-fc4x-65xv-jwjh
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-90429

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-90429, 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: iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init A user VINTF is torn down by tegra241_cmdqv_deinit_vintf(), which runs from the destroy callback and from the init-failure unwind in the alloc handler. It clears the cmdqv->vintfs[] slot and lets the iommufd core free it, but nothing serializes that against the error interrupt: tegra241_cmdqv_isr() reads cmdqv->vintfs[idx] and dereferences the vintf. A concurrent error can make the ISR read a slot mid-clear (a NULL deref) or use a vintf which is about to be freed (a use-after-free). deinit_vintf() also returns idx to the IDA before clearing the slot, so a concurrent create that reuses idx can publish its new vintf into the slot, only for this teardown to erase it again with the stale NULL store. On the other end, tegra241_cmdqv_init_vintf() publishes a new vintf with a plain store to the cmdqv->vintfs[] slot, and the ISR dereferences fields of a published vintf such as vintf->base. A plain store gives no ordering on a weakly-ordered CPU, and a stale VINTF_ERR_MAP bit on a reused idx can make the ISR pick a vintf the moment it is published, before its fields are set or tegra241_vintf_hw_init() runs. The cmdqv->vintfs[0] slot stays NULL until tegra241_cmdqv_init_structures() first creates VINTF0, so the slot 0 read needs the same NULL check. Publish every slot with an smp_store_release(), and read each slot in the ISR with an smp_load_acquire() under a NULL check, so the ISR always sees a fully built vintf or NULL. Also make deinit_vintf() clear the slot, and synchronize_irq() prior to returning idx to the IDA, so no vintf is freed under a running handler and no reused idx is clobbered.

References

Frequently Asked Questions

What is CVE-2026-90429?
CVE-2026-90429 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-90429?
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-90429?
CVE-2026-90429 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-90429?
CVE-2026-90429 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90429?
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-fc4x-65xv-jwjh",
  "modified" : "2026-09-18T18:31:32Z",
  "published" : "2026-09-17T18:32:05Z",
  "aliases" : [ "CVE-2026-90429" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init\n\nA user VINTF is torn down by tegra241_cmdqv_deinit_vintf(), which runs from\nthe destroy callback and from the init-failure unwind in the alloc handler.\nIt clears the cmdqv->vintfs[] slot and lets the iommufd core free it, but\nnothing serializes that against the error interrupt: tegra241_cmdqv_isr()\nreads cmdqv->vintfs[idx] and dereferences the vintf. A concurrent error can\nmake the ISR read a slot mid-clear (a NULL deref) or use a vintf which is\nabout to be freed (a use-after-free).\n\ndeinit_vintf() also returns idx to the IDA before clearing the slot, so a\nconcurrent create that reuses idx can publish its new vintf into the slot,\nonly for this teardown to erase it again with the stale NULL store.\n\nOn the other end, tegra241_cmdqv_init_vintf() publishes a new vintf with a\nplain store to the cmdqv->vintfs[] slot, and the ISR dereferences fields of\na published vintf such as vintf->base. A plain store gives no ordering on a\nweakly-ordered CPU, and a stale VINTF_ERR_MAP bit on a reused idx can make\nthe ISR pick a vintf the moment it is published, before its fields are set\nor tegra241_vintf_hw_init() runs.\n\nThe cmdqv->vintfs[0] slot stays NULL until tegra241_cmdqv_init_structures()\nfirst creates VINTF0, so the slot 0 read needs the same NULL check.\n\nPublish every slot with an smp_store_release(), and read each slot in the\nISR with an smp_load_acquire() under a NULL check, so the ISR always sees\na fully built vintf or NULL. Also make deinit_vintf() clear the slot, and\nsynchronize_irq() prior to returning idx to the IDA, so no vintf is freed\nunder a running handler and no reused idx is clobbered.",
  "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-90429"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a491be376abd1c80a314cdd658632c85cd660b73"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bcb82407633c3008362ad927699d985ee4981557"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f3ef4abc271a1d3d7b6715879e149c286dc8aae7"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:47Z"
  }
}