CVE-2026-90424: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-90424 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-90424 at a Glance
How to Fix CVE-2026-90424
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.
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-90424, 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
References
Frequently Asked Questions
What is CVE-2026-90424?
Which Software versions are affected?
What version fixes CVE-2026-90424?
What CWE is associated with CVE-2026-90424?
How can I check Maven dependencies for CVE-2026-90424?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-f39c-j3gp-39r5",
"modified" : "2026-09-17T18:32:05Z",
"published" : "2026-09-17T18:32:05Z",
"aliases" : [ "CVE-2026-90424" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path\n\ntegra241_cmdqv_init_structures() allocates VINTF0 with kzalloc_obj(), inits\nit, and preallocates its logical VCMDQs. Two of its error paths leak.\n\nWhen tegra241_cmdqv_init_vintf() fails it returns before VINTF0 reaches the\ncmdqv->vintfs[] array, so the devres unwind on probe failure cannot reach\nit; free it directly there.\n\nA later VCMDQ preallocation failure instead leaves VINTF0 published, and so\nthis time the unwind does reach tegra241_cmdqv_remove_vintf(), which then\nfrees it from vintf->hyp_own. But tegra241_vintf_hw_init() sets that flag\nonly afterward, from a HW read-back, so the still-uninited VINTF0 reads as\nguest-owned and leaks, with mutex_destroy() and ida_destroy() run on fields\nit never set up.\n\nDecide ownership from vintf->idx instead, the index assigned when its id is\nallocated: idx 0 is the kernel-owned VINTF0, while idx >= 1 marks a guest\nVINTF. So the in-kernel free decision in tegra241_cmdqv_remove_vintf() and\ntegra241_vintf_free_lvcmdq() now keys on idx too, and hyp_own stays a pure\nHW-readback state.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90424"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/1d2271d7df5230e4ce36bdafd17524bd004f3b3f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/417190bde0fda4ee857999a722ca90163fbec587"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/f40f3144477314b489e4bc209c06cb51679fe82b"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:17:47Z"
}
}